BUILD_CONFIG:[ Release, Debug ]

steps:

-uses:actions/checkout@v2

-uses:actions/checkout@v3

-name:Install ARM GCC on ubuntu

INSTALL:true

-{

OS:ubuntu-18.04,

OS:ubuntu-22.04,

CC:gcc-9,

CXX:g++-9

-{

OS:ubuntu-20.04,

OS:ubuntu-22.04,

CC:gcc-10,

CXX:g++-10

-{

OS:ubuntu-20.04,

OS:ubuntu-22.04,

CC:gcc-11,

CXX:g++-11,

INSTALL:true

CXX:g++-11

-{

OS:ubuntu-22.04,

CC:gcc-12,

CXX:g++-12

-{

OS:ubuntu-18.04,

VERSION:'5.0'

-{

OS:ubuntu-latest,

OS:ubuntu-20.04,

CC:clang-6.0,

CXX:clang++-6.0,

VERSION:'6.0'

-{

OS:ubuntu-latest,

OS:ubuntu-20.04,

CC:clang-7,

CXX:clang++-7,

VERSION:'7'

-{

OS:ubuntu-latest,

OS:ubuntu-20.04,

CC:clang-8,

CXX:clang++-8,

VERSION:'8'

-{

OS:ubuntu-latest,

OS:ubuntu-20.04,

CC:clang-9,

CXX:clang++-9,

VERSION:'9'

-{

OS:ubuntu-latest,

OS:ubuntu-20.04,

CC:clang-10,

CXX:clang++-10

CXX:clang++-10,

VERSION:'10'

-{

OS:ubuntu-latest,

OS:ubuntu-20.04,

CC:clang-11,

CXX:clang++-11

CXX:clang++-11,

VERSION:'11'

-{

OS:ubuntu-latest,

OS:ubuntu-22.04,

CC:clang-12,

CXX:clang++-12

-{

OS:ubuntu-latest,

OS:ubuntu-22.04,

CC:clang-13,

CXX:clang++-13,

VERSION:'13'

CXX:clang++-13

-{

OS:ubuntu-22.04,

CC:clang-14,

CXX:clang++-14

-{

OS:ubuntu-22.04,

CC:clang-15,

CXX:clang++-15,

VERSION:'15'

-{

OS:macos-10.15,

CC:clang,

CXX:clang++

-{

OS:macos-12,

CC:clang,

CXX:clang++

BUILD_CONFIG:[ Release, Debug ]

steps:

-uses:actions/checkout@v2

-uses:actions/checkout@v3

-name:Install GCC on ubuntu

steps:

-name:Checkout repository

uses:actions/checkout@v2

uses:actions/checkout@v3

-name:Initialize CodeQL

security-events:write

steps:

-name:Checkout code

uses:actions/checkout@v2

uses:actions/checkout@v3

-name:flawfinder_scan

uses:david-a-wheeler/flawfinder@8e4a779ad59dbfaee5da586aa9210853b701959c

BUILD_PLATFORM:[ x86, x64 ]

steps:

-uses:actions/checkout@v2

-uses:actions/checkout@v3

-name:Add MSBuild to PATH

uses:microsoft/setup-msbuild@master

uses:microsoft/setup-msbuild@main

-name:Build

working-directory:${{env.GITHUB_WORKSPACE}}

steps:

-name:Checkout repository

uses:actions/checkout@v2

uses:actions/checkout@v3

-name:Configure CMake

run:cmake -B ${{ env.build }}

cmake_minimum_required(VERSION 3.5)

LIST(APPENDCMAKE_MODULE_PATH

"${CMAKE_CURRENT_SOURCE_DIR}/CMake/modules")

project(ffsm2_test)

file(GLOBSOURCE_FILES"test/*.cpp""test/shared/*.cpp")

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

We as members, contributors, and leaders pledge to make participation in our

community a harassment-free experience for everyone, regardless of age, body

size, visible or invisible disability, ethnicity, sex characteristics, gender

identity and expression, level of experience, education, socio-economic status,

nationality, personal appearance, race, religion, or sexual identity

and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,

diverse, inclusive, and healthy community.

Examples of behavior that contributes to creating a positive environment include:

Examples of behavior that contributes to a positive environment for our

community include:

* Using welcoming and inclusive language

* Being respectful of differing viewpoints and experiences

* Gracefully accepting constructive criticism

* Focusing on what is best for the community

* Showing empathy towards other community members

* Demonstrating empathy and kindness toward other people

* Being respectful of differing opinions, viewpoints, and experiences

* Giving and gracefully accepting constructive feedback

* Accepting responsibility and apologizing to those affected by our mistakes,

and learning from the experience

* Focusing on what is best not just for us as individuals, but for the

overall community

Examples of unacceptable behaviorby participantsinclude:

Examples of unacceptable behavior include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances

* Trolling, insulting/derogatory comments, and personal or political attacks

* The use of sexualized language or imagery, and sexual attention or

advances of any kind

* Trolling, insulting or derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or electronic address, without explicit permission

* Other conduct which could reasonably be considered inappropriate in a professional setting

* Publishing others' private information, such as a physical or email

address, without their explicit permission

* Other conduct which could reasonably be considered inappropriate in a

professional setting

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Community leaders are responsible for clarifying and enforcing our standards of

acceptable behavior and will take appropriate and fair corrective action in

response to any behavior that they deem inappropriate, threatening, offensive,

or harmful.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject

comments, commits, code, wiki edits, issues, and other contributions that are

not aligned to this Code of Conduct, and will communicate reasons for moderation

decisions when appropriate.

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

This Code of Conduct applies within all community spaces, and also applies when

an individual is officially representing the community in public spaces.

Examples of representing our community include using an official e-mail address,

posting via an official social media account, or acting as an appointed

representative at an online or offline event.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team atandrew.gresyk@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Instances of abusive, harassing, or otherwise unacceptable behavior may be

reported to the community leaders responsible for enforcement at

andrew-gresyk@users.noreply.github.com.

All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the

reporter of any incident.

Community leaders will follow these Community Impact Guidelines in determining

the consequences for any action they deem in violation of this Code of Conduct:

**Community Impact**: Use of inappropriate language or other behavior deemed

unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing

clarity around the nature of the violation and an explanation of why the

behavior was inappropriate. A public apology may be requested.

**Community Impact**: A violation through a single incident or series

of actions.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

**Consequence**: A warning with consequences for continued behavior. No

interaction with the people involved, including unsolicited interaction with

those enforcing the Code of Conduct, for a specified period of time. This

includes avoiding interactions in community spaces as well as external channels

like social media. Violating these terms may lead to a temporary or

permanent ban.

**Community Impact**: A serious violation of community standards, including

sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public

communication with the community for a specified period of time. No public or

private interaction with the people involved, including unsolicited interaction

with those enforcing the Code of Conduct, is allowed during this period.

Violating these terms may lead to a permanent ban.

**Community Impact**: Demonstrating a pattern of violation of community

standards, including sustained inappropriate behavior, harassment of an

individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within

the community.

This Code of Conduct is adapted from the[Contributor Covenant][homepage], version 1.4, available at[http://contributor-covenant.org/version/1/4][version]

This Code of Conduct is adapted from the[Contributor Covenant][homepage],

version 2.0, available at

https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by[Mozilla's code of conduct

enforcement ladder](https://github.com/mozilla/diversity).

[homepage]:https://www.contributor-covenant.org

[homepage]:http://contributor-covenant.org

[version]:http://contributor-covenant.org/version/1/4/

For answers to common questions about this code of conduct, see the FAQ at

https://www.contributor-covenant.org/faq. Translations are available at

https://www.contributor-covenant.org/translations.

MIT License

Copyright (c)2021 Andrew Gresyk

Copyright (c)2023 Andrew Gresyk

Permission is hereby granted, free of charge, to any person obtaining a copy

of this software and associated documentation files (the "Software"), to deal

- Visual Studio: 2015,**2017, 2019, 2022**

- GCC:**5, 6, 7, 8, 9, 10, 11**

- GCC:**5, 6, 7, 8, 9, 10, 11, 12**

- ARM GCC:**9**

- Clang:3.7, 3.8,**3.9, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13**

- AppleClang:**12, 13**

- Clang:**3.9, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15**

- AppleClang:**12, 13, 13**

(Currently CI-tested toolchainsarein**bold**)

(Currently CI-tested toolchains in**bold**)

-**[HFSM2](https://hfsm.dev)**: High-Performance**Hierarchical** Finite State Machine

-**[HFSM Mono](https://font.hfsm.dev/)**: Monospaced bitmap Unicode fonts for HFSM2 and FFSM2 libraries

- Fully static, no dynamic allocations

- Uses inline-friendly compile-time polymorphism, no virtual methods are used

- Type-safe transitions:`FSM.changeTo<TargetState>()` with optional payloads

- Flexible configuration using`FFSM2_ENABLE_*` macros

- Scaleable, supports robust state re-use via state injections

- Gamedev-friendly, supports explicit`State::update()`

- Also supports traditional event-based workflow with`State::react()`

- Inspect anything: previous and current transitions, state activation status, and more!

- Game AI-friendly with dynamic planning support

-**[Debug-assisted](https://gresyk.dev/features/2018/01/15/hfsm-magic.html)**, includes automatic structure and activity visualization API

- Built-in logging support

- Twitter:**[@andrew_gresyk](https://www.twitter.com/andrew_gresyk)**

- Discord:**[HFSM.dev](https://discord.gg/v4t3tzh)**

- Discord:**[HFSM.dev](https://discord.gg/ZfWjhFj)**

- Gitter:**[andrew-gresyk/FFSM2](https://gitter.im/andrew-gresyk/FFSM2)**