Right. Maybe I should say "unique" or "private" (... that is a reserved keyword), because it may collide with another cpp when joined by unity, but they are not exposed outside.
On Mon, 27 Nov 2023 at 18:02, Even Rouault <[email protected]> wrote: > > Le 27/11/2023 à 17:43, Javier Jimenez Shaw a écrit : > > Hi Even > > > > Thanks for the work. As you say, having the option is useful. It is > > true that anonymous namespaces are not anonymous any more, > > Depends on how you resolve the collisions, but the concept of anonymous > namespace still exists > > That is, you can't do anymore > > a.cpp: namespace { struct foo{}; } > b.cpp: namespace { struct foo{}; } > > But you can do: > > a.cpp: namespace { struct foo{}; } > b.cpp: namespace { struct bar{}; } > > Regarding to code external to PROJ, the anonymity is still preserved > > > -- > http://www.spatialys.com > My software is free, but my time generally not. > >
_______________________________________________ PROJ mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/proj
