rotor VS tolc

If your architecture fits into inter-process messaging, i.e. spawn threads which do similar or different tasks and inform each other via messages, try to use actor framework, i.e. rotor (disclaimer: I'm the author). If there is a need to expand messaging even more, i.e. across the network, you can try to use caf, which provides that facility out of the box.

What you achieved, is handlers decoupling, i.e. when one handler knows nothing about other handler, which leads to good application testability. However, with standard promise/future bases messaging, if performance matters (and it usually does, otherwise why use C++?), i doubt that your implementation overwhelms the performance of specialized actor libraries, like sobjectizer ("batteries included" actors toolbox) or rotor (DIY-like actor constructor set; disclaimer: I'm the author of it).

I have been reading the documents from Boost.fibre and Boost.Signals2 which I could use, maybe ASIO for async. I also checked ZeroMQ (this seems to be more or less "only" for networking), Copper and Rotor. If this were just a simple MCU project I would just take the FreeRTOS and would have everything I need. Now I'm just lost how to structure my code / how to realize my main loop.

I would like to present my project rotor, which is event loop friendly C++ actor micro framework with Erlang-like microframework with supervising capabilities.

rotor actor library (I'm the author) was designed to solve similar problem, which I named "actor intrusiveness", when almost every piece of code should be written in form of actor, and, the working threads, which spin actors, are out of your control.

PS. I'm the author of rotor framework )

May be actor frameworks like caf, sobjectizer or rotor is something, that you are looking for.

I love CLI11! It has been pretty easy all the way through. Used to use lyra before but since I wanted to have subgroups in Tolc I had to switch. Great job on CLI11 if the author is in the chat :)

I'm working on a project called Tolc that is generating bindings from C++ to other languages. When creating bindings to a class MyClass, it needs to be defined before any code using that class (for example a function that returns an instance of it). Therefore I needed to know in which order to define things. Honestly I just had so much fun solving this problem (using some C++20 and features) that I wrote a post so sum it all up:

Hi everyone!

Some friends and I were unhappy with how much work it was to use C++ from other languages. We were working in the optimizations industry and often had to prototype with python. Eventually, we created a tool to make it easier for C++ to talk to python (by generating pybind11). Later, javascript via WebAssembly was added as well. It's now at a point where it's very easy to just create a C++ library and use it from any of those languages without change. We're planning on slowly adding more languages as needed/requested. The next on the list are Swift and Kotlin.

It does not require any change to your existing public interface, but simply reads it and creates the bindings off of that. It should also work on Linux (Debian), MacOS, and Windows (Visual Studio). Here's a small demo if you'd like to test:

https://github.com/Tolc-Software/tolc-demo

And here are the repositories with the source code:

https://github.com/Tolc-Software/tolc - The executable

https://github.com/Tolc-Software/frontend.py - The python bindings generator

https://github.com/Tolc-Software/frontend.wasm - The WebAssembly bindings generator

https://github.com/Tolc-Software/Parser - The C++ parser

It is dual licensed with AGPL and, if someone wants, a commercial license as well.

Would be cool if someone finds it useful!

https://github.com/Tolc-Software/tolc - The executable and CMake wrappers

I’m just gonna drop this here: https://github.com/Tolc-Software/tolc