> > If you're still unsure, just look around on any well known >> OSS projects, or MS source code (the CRT for example), >> or even official MS Windows headers to see how they >> #include other Windows headers. >> > > Thank you, but I would see what ISO have to say on this subject, not GNU or > MS. I haven't clear what a HEADER is and what a FILE is. The syntax with <> > is only for HEADERs. An HEADER is not a FILE, in the sense that it doesn't > have to exist as a file, which doesn't necessarily mean that a FILE can't be > considered a HEADER.
Good luck finding an ISO standard on the net (for free) :) IMO there is no difference whether it's a FILE or HEADER as the standard merely controls in which _order_ to check different dirs for the specified FILE/HEADER. This means the standard most probably won't use the words "systems headers", or "OS headers", but rather something like "default include dir", dir specified by user (INCLUDE envvar, -I cmdline option), and dir of compiled source file. Of course you don't have to believe me, if you find some more authentic information, post it here. Brgds, Viktor
_______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
