Development of version 2.0 of Hinterlib/Neopolitan has started. I do say “Hinterlib/Neopolitan” as I have high confidence that the two libraries will be whole again. Here’s a brief list of the changes I’ve made just lately:
I’ve restricted the compiler scope to GCC, LLVM and FCC, which greatly simplifies the boilerplate.
I’ve improved the semantics of the synthetic definitions feature of Slick/Inbound by differentiating target peculiarity monikers (ergo, are we running on Linux, are we on ARM or what, do we have floating-point, is it hardware-based, and so on) from configuration options that the user may set (ergo, stuff like disabling GUIs or dropping in other algorithms for features).
I also added a sanity check into every header so when things go wrong, the obvious fix is sure to be made first: be sure you are using a supported compiler and the Slick or Inbound build tools. A library like Hinterlib cannot be practically portable without making some compromises on abstract portability.
Keep reading with a 7-day free trial
Subscribe to Nichstack to keep reading this post and get 7 days of free access to the full post archives.