gklingler / sharedlibsdemo Goto Github PK

I just found your repo about the OS portable shared libraries and it looks great.

I have a project where not only does it have to be OS portable, the main codebase has a architecture where there is the main control code, which then given a specific variant would need to call that variant's state machine.

At the source level, it would be a matter of having a data structure with the function pointers for each of the state machine functions. However, I cannot know all the possible variants upfront and I would like it to be forward compatible with statemachine plugins.

Not sure how best to do this...
I was thinking that the baseline code could be calling a shared library that somehow is configured to "bind" to a specific statemachine plugin. then the adding of the new statemachine can be done at the system level.

Alternatively, each statemachine could be a separate executable that registers with the baseline codebase using IPC, but this runs into runtime OS compatibility issues.

Any advice is much appreciated!

To summarize, we have an OS portable codebase (in C) that is calling a standardized statemachine through a predefined set of interface functions. There will be many different statemachine variants, and the exact type (name) of all the future statemachines is unknown.

Some sane way to create the set of OS portable statemachines that all are called by the OS portable baseline code is needed.