[sword-devel] #INCLUDE

sword-devel@crosswire.org sword-devel@crosswire.org
Tue, 22 May 2001 08:07:02 EDT


--part1_a9.15e8ae4f.283bb066_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 5/22/2001 5:20:35 AM Eastern Daylight Time, 
scribe@crosswire.org writes:


> Not sure about the #include issue.  It is my impression that #include
> "file" looks for file in the SAME directory as the cpp file, whereas
> #include <file> searches the entire include path.  Not sure if it
> working in borland is their own extension.  I'll try under unix and let
> ya know.  Someone should probably refer the ANSI spec.
> 

Yes, that is correct.

--part1_a9.15e8ae4f.283bb066_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

<HTML><FONT FACE=arial,helvetica><FONT  SIZE=2>In a message dated 5/22/2001 5:20:35 AM Eastern Daylight Time, 
<BR>scribe@crosswire.org writes:
<BR>
<BR>
<BR><BLOCKQUOTE TYPE=CITE style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">Not sure about the #include issue. &nbsp;It is my impression that #include
<BR>"file" looks for file in the SAME directory as the cpp file, whereas
<BR>#include &lt;file&gt; searches the entire include path. &nbsp;Not sure if it
<BR>working in borland is their own extension. &nbsp;I'll try under unix and let
<BR>ya know. &nbsp;Someone should probably refer the ANSI spec.
<BR></FONT><FONT  COLOR="#000000" SIZE=3 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></BLOCKQUOTE>
<BR></FONT><FONT  COLOR="#000000" SIZE=2 FAMILY="SANSSERIF" FACE="Arial" LANG="0">
<BR>Yes, that is correct.</FONT></HTML>

--part1_a9.15e8ae4f.283bb066_boundary--