From: Erik Max Francis <max AT alcyone DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: #include "..." versus <...>
Date: Thu, 10 Jul 1997 20:03:58 -0700
Organization: Alcyone Systems
Lines: 30
Message-ID: <33C5A29E.FDFD0C@alcyone.com>
References: <Pine DOT D-G DOT 3 DOT 91 DOT 970707122408 DOT 1203A-100000 AT dg1>
NNTP-Posting-Host: newton.alcyone.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Art S. Kagel wrote:

[Confused attributions deleted; you replied to my message, but didn't
quote any of it]

> From K&R 2nd Ed., Section 4.11:
> 
> "File inclusion ... If the filename is quoted, searching for the file
> typically begins where the source program was found; if it is not found
> there, or if the name is enclosed in < and >, searching follows an
> implementation-defined rule to find the file."
> 
> 'Nuff said?

ANSI C doesn't say _anything_ about how the stuff inside the quotes or
angle brackets is translated to the filesystem (which makes sense, because
different operating systems have different path separators, etc.).  All it
does say is that #include "..." defaults to an #include <...> form if the
quoted search fails.

As such, this _is_ a platform-dependent question, and is (believe it or
not) relevant to comp.os.msdos.djgpp.

-- 
       Erik Max Francis, &tSftDotIotE / email / max AT alcyone DOT com
                     Alcyone Systems /   web / http://www.alcyone.com/max/
San Jose, California, United States /  icbm / 37 20 07 N  121 53 38 W
                                   \
           "All the gods are dead / except the god of war."
                                 / Eldridge Cleaver