reserved identifier violation
Closed this issue · 5 comments
I would like to point out that identifiers like "__GB_NAMESPACE_START" and "gb__string_realloc" do eventually not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?
I do know this but I have never seen this be a problem in the wild, ever. If you can show me an example when this is a problem please do so.
However, I will be retiring gb.hpp soon and completely replacing it with gb.h. gb.h will be C compatible and be a better tool all round for my needs. gb.hpp was good but I am find gb.h to better for my uses as I am programming in C and C-styled C++ more and more these days.
How do you think about to avoid that this software depends on undefined behaviour?
Which parts (apart from the naming of those identifiers)?
Would you like to change the usage of (double) underscores in affected identifiers?
I won't need to as I will remove this library soon and fully replace it with gb.h. gb.h is still missing many features but they won't be hard to implement.