Re:In C++ modules globally unique module names seem to be un...
by juliangmp on Thursday October 02, 2025 @04:08AM
(#45447299)
Conflicts with symbol names are a thing yes, but if I use some open source library I don't have to care about how they named their translation units. Header files might clash, which is also bad design IMO, so the reasonable thing and what I've made my default is to have a subdirectory with the library name in the include path (I.e. inc/MyLib/foo.h instead of inc/foo.h).
[ Parent
| on HN ]
There are no comments on this comment yet.