PpHd
PpHd
There are currently no better way to do it. I have a few questions: Do you need: * a full encapsulation? (type + functions are encapsulated) * function encapsulation? (type...
> Wouldn't that explode the code size since the same functions are generate multiple times in each .c file that consumes the header? Well it depends. First if you don't...
This solution would do the job. Some C container libraries already do this. Note that the current macro _DEF could not be used for this (another one will be needed)...
I am not sure I want to implement such mechanism. It will go against a standardization of such library: every user of the library will use different naming, and it...
The main problem for the remaining emplace functions is to find how to name the emplace function: * from the set of emplace functions of the key (empty, suffix1a, ...)...
I'll probably go on with "name_key_emplace_suffix1a_val_suffix1b" with suffix1a being the key and suffix1b the value even if it is not perfect.
Change from _str to _cstr has been done.
I postpone change to _fstr. _cstr will be good enough.
You can already define your own types without the _t suffix, if you want, by using the \_DEF\_AS macros instead of the \_DEF ones.