RE: [Cppunit-devel] Re: [cppunit - Open Discussion] RE: Why Syste m Includes?

[Summerwill, B. <BSu...@eu...>]

>> I'd also like to tone this down a bit.  In fact, the difference
>> between <header> and "header" is system-dependent
>>   <http://www.eskimo.com/~scs/C-faq/q10.8.html>.  
>> But it still seems to me that <cppunit/foo> is the correct choice in
>> this case.  Other "3rd party" libs, like Qt and Gtk use <>-style
includes.

Thanks for the reference.  I was about to ask if you could elaborate on the
difference between the two types of #includes.  It had always been my
understanding that <> tried the include paths, and that "" tried the
same directory as the file doing the include, then did the standard search -
but I (incorrectly) thought that this behaviour was guaranteed.

Out of interest, does anyone know which compilers don't implement this
"normal" behaviour?  I know that GCC and MSVC++ are both "standard"
in this respect.


Cheers,
Bob

-----Original Message-----
From: Steve M. Robbins [mailto:ste...@vi...]
Sent: 28 September 2001 03:17
To: CppUnit Development
Subject: Re: [Cppunit-devel] Re: [cppunit - Open Discussion] RE: Why
System Includes?


On Thu, Sep 27, 2001 at 11:00:40AM -0400, Steve M. Robbins wrote:
> On Thu, Sep 27, 2001 at 07:43:57AM -0700, no...@so... wrote:

> > For the cpp file it is ok. #include <filename> states that include path
indicate
> > with /I option are search first, then those of the environment variable.
> 
> Careful -- you're getting into system-dependent behaviour here!
> I've never met a C compiler that used an environment variable to change
> the header include path!

I take this back.  GCC does pay attention to some environment variables.
On the other hand, I've never seen them in use.


> All the headers in include/cppunit *must* include the other headers
> using <cppunit/...> notation.

I'd also like to tone this down a bit.  In fact, the difference
between <header> and "header" is system-dependent
  <http://www.eskimo.com/~scs/C-faq/q10.8.html>.  
But it still seems to me that <cppunit/foo> is the correct choice in
this case.  Other "3rd party" libs, like Qt and Gtk use <>-style includes.

-S

-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants


_______________________________________________
Cppunit-devel mailing list
Cpp...@li...
https://lists.sourceforge.net/lists/listinfo/cppunit-devel