Hello everyone,

I have recently been writing some code which uses ActiveMQ-CPP library. Due to the fact, that I have used C++17 and C++20, I started writing some RAII-related code for the library types/functions (e.g. custom deleters), and it made me wonder: would it not be good to provide some of those functionalities on library level? Since C++11 playing around with new/delete is no more needed, same about threading API. Please don't get me wrong: I really appreciate the API that decaf:: provides, yet in the end I tend to to write my own wrappers/adapters to be more-less in-line with contemporary C++ standard lib. Last but not least, auto_ptr deprecation warnings look just ugly on in my build log and maybe at least moving away from those should do no harm.

I am keen on contributing to the library by migrating at least parts of it to newer C++ standard (I am doing sth similar anyway), however I would need some guidelines on what is potentially safe to touch/migrate and how to approach it, e.g. what C++ target standard should be.

If this is totally undesired and "backwards compatibility is king" feel free to turn me down.

Best regards,
Aleksander Miera

Reply via email to