Closed elfring closed 10 years ago
Or maybe use a common prefix for the include guards like R3_
How do you think about to reduce the probability for name clashes a bit more?
I agree that NODE_H
and LIST_H
are too generic for include guards but using UUIDs is such an overkill IMHO; It looks weird too. Personally I use this format:
// header.h
#ifndef MY_PROJECT_HEADER_H_INCLUDED
#define MY_PROJECT_HEADER_H_INCLUDED
// ...
#endif
The probability of it conflicting with other libraries include guard should not be that high.
I think adding a prefix R3_
will be better. :-)
Fixed in 5a10c82 and 288cdc9
It would have been better to group such renaming into a single commit with a reference for this issue, wouldn't it?
Will the affected include guards get the project prefix at least?
I find that include guards like "NODE_H" and "LIST_H" are too short for the safe reuse of your header files. How do you think about to make them unique by appending a kind of UUID?