
7 Sep
2008
7 Sep
'08
5:42 p.m.
Michael Fawcett wrote:
Now, isn't there a slight performance and semantic difference that should lead to using "" and not <>? Doesn't <> mean search compiler dependent search path for file, then search user supplied paths in order supplied, and "" means search user supplied path in order supplied, then fall back to compiler dependent path?
No, while this is all implementation defined, on every compiler I've used <> will always search paths supplied with -I directives before system paths. One could argue that "" is less efficient because it *may* search paths relative to the current file before looking at -I paths. But frankly any argument on efficiency grounds is likely to be fallacious: all strictly IMO of course! John.