On Jan 28, 2009, at 12:24 PM, H.J. Lu wrote:
On Wed, Jan 28, 2009 at 12:21 PM, Chris Lattner
wrote:
On Jan 28, 2009, at 11:51 AM, H.J. Lu wrote:
Hi,
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"
Any comments?
I strongly recommend against thi
"H.J. Lu" writes:
> 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?
Yes. Put this at top level (i.e., in the same directory where the
directory "foo" is):
Foo/Foo.h foo/foo.h
Then #include "Foo/Foo.h" wil
On Wed, Jan 28, 2009 at 12:48 PM, Ian Lance Taylor wrote:
> "H.J. Lu" writes:
>
>> On Wed, Jan 28, 2009 at 12:32 PM, Ian Lance Taylor wrote:
>>> "H.J. Lu" writes:
>>>
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"
Any comme
"H.J. Lu" writes:
> On Wed, Jan 28, 2009 at 12:32 PM, Ian Lance Taylor wrote:
>> "H.J. Lu" 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.
>>
>> h
On Wed, Jan 28, 2009 at 12:32 PM, Ian Lance Taylor wrote:
> "H.J. Lu" 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/cppinte
H.J. Lu wrote:
On Wed, Jan 28, 2009 at 12:21 PM, Chris Lattner wrote:
On Jan 28, 2009, at 11:51 AM, H.J. Lu wrote:
Hi,
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"
Any comments?
I strongly recommend against this, unless this is only a "last chan
"H.J. Lu" 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
Ian
On Wed, Jan 28, 2009 at 12:21 PM, Chris Lattner wrote:
>
> On Jan 28, 2009, at 11:51 AM, H.J. Lu wrote:
>
>> Hi,
>>
>> I got a request to try "FOO.H" if foo.h doesn't exist when dealing
>> with
>>
>> #include "foo.h"
>>
>> Any comments?
>
> I strongly recommend against this, unless this is only a
On Jan 28, 2009, at 11:51 AM, H.J. Lu wrote:
Hi,
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"
Any comments?
I strongly recommend against this, unless this is only a "last chance"
fall back.
From a performance standpoint, if you have -Idir1 -I
On Wed, Jan 28, 2009 at 12:03 PM, David Daney wrote:
> H.J. Lu wrote:
>>
>> Hi,
>>
>> I got a request to try "FOO.H" if foo.h doesn't exist when dealing
>> with
>>
>> #include "foo.h"
>>
>> Any comments?
>>
>
> How about "Foo.h", "FOo.H", etc.?
>
> I have found as many errors with mixed case screw
H.J. Lu wrote:
Hi,
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"
Any comments?
How about "Foo.h", "FOo.H", etc.?
I have found as many errors with mixed case screw-ups as with the
'single case' variety you mention.
Would you want to make it full
Hi,
I got a request to try "FOO.H" if foo.h doesn't exist when dealing
with
#include "foo.h"
Any comments?
Thanks.
--
H.J.
12 matches
Mail list logo