Markus Elfring

:thought_balloon: Would you like to take [the C++ guideline “R.11: Avoid calling new and delete explicitly”](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#r11-avoid-calling-new-and-delete-explicitly "Recommendations around allocation and deallocation") better into account?

>…, this code is intended to be used in a C environment, … :eyes: Some `delete` statements are obviously still used in your C++ source files. >Raw pointer usage is...

>…, smart pointers cannot be used here, :eyes: I got an opposite impression for C++ source code which is generally improvable. >at least I cannot see another way. :thought_balloon: Your...

Known development tools can remind (interested programmers and reviewers) on possible code improvements already. :thinking:

>But I want to know if _you_ can propose an improvement. I obviously did that for various software components. :thought_balloon: I hope that development interests will grow for reported change...

:thought_balloon: * Do you care for advices from linked information sources at all? * Would you dare to read them once more?

:thought_balloon: How do you think about to avoid that this software [depends on undefined behaviour](https://www.securecoding.cert.org/confluence/display/c/CC.+Undefined+Behavior#CC.UndefinedBehavior-ub_106 "Avoiding undefined behaviour?")?

:thought_balloon: I would appreciate if you would care more for standard compliance also according to affected implementation details.

>… if you explained the problem as I asked for. :thought_balloon: [This software tampers still with the reserved name space](https://en.cppreference.com/w/cpp/language/identifiers#In_declarations "Documentation"), doesn't it? >…, so I'll handle this with low...

:thought_balloon: Would you like to care for standard compliance?