On Wed, Jan 28, 2009 at 12:48 PM, Ian Lance Taylor <i...@google.com> wrote: > "H.J. Lu" <hjl.to...@gmail.com> writes: > >> On Wed, Jan 28, 2009 at 12:32 PM, Ian Lance Taylor <i...@google.com> wrote: >>> "H.J. Lu" <hjl.to...@gmail.com> writes: >>> >>>> I got a request to try "FOO.H" if foo.h doesn't exist when dealing >>>> with >>>> >>>> #include "foo.h" >>>> >>>> Any comments? >>> >>> Please, no. >>> >>> They could use header.gcc instead. >>> >>> http://gcc.gnu.org/onlinedocs/cppinternals/Files.html >>> >> >> Will it work on pathnames? > > Normally the file is placed where the header file lives, and gives > alternate names which may be used to open the header file. >
Say I have #include "Foo/Foo.h" I want to map it to foo/foo.h on disk. Can I map Foo to foo with header.gcc in directory, foo? Thanks. -- H.J.
