RuntimeCompiledCPlusPlus VS semver

hscpp (Hotswap C++) is an experimental library I created which allows you to hot-reload C++. It was heavily inspired by Runtime Compiled C++, and works by linking DLLs into your project at runtime.

The only recent attempt to make something like this practical, as far as I know, was RCCpp. Going by the GH activity, it looks like it kind of went nowhere.

FYI I maintain a list of runtime compiled C++ approaches on this wiki: https://github.com/RuntimeCompiledCPlusPlus/RuntimeCompiledCPlusPlus/wiki/Alternatives

There is https://github.com/RuntimeCompiledCPlusPlus/RuntimeCompiledC...

The idea is to use virtual functions, and recompile new classes into a shared library. The shared lib is linked into the running program, and old instances of the classes are deleted and replaced by new instances constructed from the share library.

I am working on a library using the same (stolen) idea here:

https://github.com/jheruty/hscpp

Proof of concept demo:

https://m.youtube.com/watch?v=pjGngeKgni8

hscpp is still very alpha, and I’m sure I’ll find lots of bugs as I work on a “real” demo. In contrast, Runtime Compiled C++ is quite mature and is used in real game projects.

Note that this approach very much limits your architecture. For example, you won’t be able to use statics, as the newly compiled shared libraries won’t see them.

It’s a finicky thing, worth it to me, but not something you can just plop in to an established project.

Well of course it's possible to generate executable code at runtime in C++ since clang itself is written in C++, but it's definitely a much larger undertaking, but there's two such efforts I know of, Cling and RuntimeCompiledCPlusPlus.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/

Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.

https://github.com/semver/semver/releases

All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)

If you're using semver, read the spec it's not overly long or hard to understand.

Semantic versioning actually has a clear rule about this: