On 27 Dec 2008, at 10:19, Tim Moore wrote: > Correctness, in the sense that I can't compile SimGear without this > change. Also > consistency, since in SimGear we consistently refer to headers from > other > SimGear modules using #include <simgear/...>. The important part of > the change > is adding "simgear" to the include path. > > "<>" doesn't necessarily mean "public header", just (at least, in > gcc) "look in > standard places, including those added by -I."
Interesting - I'm testing all these changes on a VMware-Ubunutu image, and this compiled fine. I do have simgear 'installed' to /usr/local though, maybe that means it's picking up the installed headers anyway. The different semantic meanings of <> vs "" is something I've struggled with in the past, and there are some Mac-specific conventions which are probably rather too strongly embedded in my brain, so I shall simply cease to worry about this, and stick to the house style. As you noted, GCC doesn't make much distinction at all. James ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
