Lars Clausen wrote:
>
> bash-2.03$ find . -name \*.c | xargs grep \
> '# *include *["<]config\.h[">]' | wc -l
> 161
>
We could of course also include the TAB in case that's used in some of
the files, but this still doesn't check that the inclusion is done
_first_, and besides...
> It's a bloody mess. Is it supposed to be <config.h> or "config.h"? And
> we're still missing 67 of them.
...this still doesn't make much difference to your main point here,
anyway.
And we're down to only 67 now, which should be easy to locate...
According to my ancient "ABC" on C that happened to be on my bookshelf
nearby right now (I program mostly in C++ now, so C doc is sparse...), I
"refreshed" my knowledge a little on this subject. It says on the
subject <> vs "":
""
A search for the file is made first in the current directory and then in
the standard places.
<>
the preprocessor looks for the file only in the standard places and not
in the current directory.
...but the standard might have updated itself many times after that ;-)
However, this suggests that "" is the most inclusive form (and allows
for even local versions in the sub-dirs, which might not be a good
idea), so maybe this should be chosen?
-+-Ben-+-
