From:	frenchc AT cadvision DOT com (Calvin French)
Newsgroups:	comp.os.msdos.djgpp
Subject:	#include "..." versus <...>
Date:	5 Jul 1997 17:40:56 GMT
Organization:	Reham Salad
Lines:	19
Message-ID:	<5pm0v8$45io@elmo.cadvision.com>
NNTP-Posting-Host:	ts14ip243.cadvision.com
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I know this isn't djgpp specific, but I'd rather as here (I like you people 
better :-)

I have noticed that <...> allows for directories, whereas if I recall "..." 
doesn't pay attention to directories, or something like that. Really, i have 
to keep part of my program in separate directories and some files have the 
same names. Previously I used <...>, but now I have switched to "..." 
because I understand that "..." is more for dynamically-changing files 
(i.e., non-standard or libraried includes) wherease <...> is more for 
standard library includes. This is all very strange to me. What's the diff 
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 
part static. But I need to use <...> to differentiate headers by directories 
(for example, I have <spr/base.h> and <spr/batt/base.h> which will confuse 
the includer if I use quotes) This is all very strange to me, but I never 
bothered asking because until now I was not so concerned about good style...

- Calvin -

- Raw text -