---

Kort spørgsmål:

Hvad er forskellen på

#include "Whatever.h" og

#include <Whatever.h>

i VC++





Tak, Teis

---

On Thu, 8 May 2003 20:18:05 +0200, Teis Draiby wrote:

> #include "Whatever.h" og

Søger først i current path og dine private include-paths.

> #include <Whatever.h>

Søger udelukkende blandt systemets header-filer.

/\/\\ads Orbesen Troest

---

Mads Orbesen Troest <mads@troest.NEVERMORE.dk> writes:

> On Thu, 8 May 2003 20:18:05 +0200, Teis Draiby wrote:
>
> > #include "Whatever.h" og
>
> Søger først i current path og dine private include-paths.
>
> > #include <Whatever.h>
>
> Søger udelukkende blandt systemets header-filer.

Nu spoerger han godtnok specifikt til VC++, som jeg ikke lige kender
til, men er det ikke 'normalt' at;

"whatever.h" er i fht. current path, dvs. "../other/whatever.h" ogsaa
ville vaere ok, og

<whatever.h> er i include paths (baade 'system' og dem man angiver
med -I til compileren).


Mvh,

--
___
Soren Davidsen / o\
Math student, ICSMA (_____)
__ http://www.tanesha.net/ _________________________________(___)_______

---

Soren Davidsen skrev:
> Mads Orbesen Troest <mads@troest.NEVERMORE.dk> writes:
>
>
>>On Thu, 8 May 2003 20:18:05 +0200, Teis Draiby wrote:
>>
>>
>>>#include "Whatever.h" og
>>
>>Søger først i current path og dine private include-paths.
>>
>>
>>> #include <Whatever.h>
>>
>>Søger udelukkende blandt systemets header-filer.
>
>
> Nu spoerger han godtnok specifikt til VC++, som jeg ikke lige kender
> til, men er det ikke 'normalt' at;
>
> "whatever.h" er i fht. current path, dvs. "../other/whatever.h" ogsaa
> ville vaere ok, og
>
> <whatever.h> er i include paths (baade 'system' og dem man angiver
> med -I til compileren).
>
C standarden er ikke ret klar på dette punkt (citat fra C99 draft):

2 A preprocessing directive of the form
# include <h-char-sequence> new-line
searches a sequence of implementation-defined places for a header
identified uniquely by the specified sequence between the < and >
delimiters, and causes the replacement of that directive by the entire
contents of the header. How the places are specified or the header
identified is implementation-defined.

3 A preprocessing directive of the form
# include "q-char-sequence" new-line
causes the replacement of that directive by the entire contents of the
source file identified by the specified sequence between the "
delimiters. The named source file is searched for in an
implementation-defined manner. If this search is not supported, or if
the search fails, the directive is reprocessed as if it read
# include <h-char-sequence> new-line
with the identical contained sequence (including > characters, if any)
from the original directive.

Normalt bruges #include <what.h> til system header (compilerens egne)
filer, hvorimod formen #include "mine.h" bruges til dine egne header
filer.

/b

---

Tak skal i have!

Teis