From: Matthew Mastracci <mmastrac AT acs DOT ucalgary DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: #include "..." versus <...>
Date: Sun, 6 Jul 1997 00:51:36 -0600
Organization: The University of Calgary
Lines: 32
Message-ID: <5pnfbf$n6k@ds2.acs.ucalgary.ca>
References: <5pm0v8$45io AT elmo DOT cadvision DOT com>
NNTP-Posting-Host: mmastrac AT acs2 DOT acs DOT ucalgary DOT ca
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <5pm0v8$45io@elmo.cadvision.com>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On 5 Jul 1997, Calvin French wrote:

> here? I'd rather just use "..." with header files specific to the particular 
> application at hand, and <...> to those which can be considered for the most 

Normally (by tradition) <...> is used to specify a file that is part of
an unchanging library, while "..." refers to a header file in your
project.

The semi-standard approach is that with <...>, the include directories are
scanned for the file.  With "...", the current directory is checked, and
if the file isn't found, the rest of the directories are checked.  This is
probably the case with GNU's C++, but you may want to read the INFO files.

As for relative paths, the compiler should be picking up "stuff\foo.h" as
the file foo.h in the stuff directory off the project directory and
"foo.h" as the file foo.h in the main project directory. If it doesn't,
there may be a configuration problem. 

Also, try compiling with:

gcc [filename] -v

This will show you which directories are searched for include <...> and
"..." files.

/\/\att /\/\astracci                  mmastrac AT acs DOT ucalgary DOT ca

GCS/GE    d- s+:+ a--- C++++ UA P+ L E-- W+ N++ o K+ w+ O M- V 
          PS++ PE++ Y+ PGP t+++ 5+++ X++ R++ tv+ b+++ DI++++ I 
          G++ e h r* z?