Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!xadmx!BPB9204%TAMSTAR.BITNET@cunyvm.cuny.edu
From: BPB9204%TAMSTAR.BITNET@cunyvm.cuny.edu
Newsgroups: comp.lang.pascal
Subject: USING #include FILES.
Message-ID: <18237@adm.BRL.MIL>
Date: 29 Jan 89 02:03:00 GMT
Sender: news@adm.BRL.MIL
Lines: 23


  Seeing some of the different replys about include files makes me write.
There are two different formats of include:
   #include "file_name"
and
   #include <file_name>
 T.
they do the same, but how they do it is the difference.  #include "file" instruc
ts
the compiler to search first the same directory the file that contains #include
resides in, then search other directories.
#include <file> is to search only in certain special directories where standard
system files are located.

At my university's vax using UNIX (Ultrix v1.0, I think) we use #include <f>.
I think if you are on a PC, you'd try #include "file" - because related file
are stored in the same directory on a PC, and on a vax, so many users have
similar files spread all around.
  I hope this info helps. (It was in the book, C as a second Language, by
Tomasz Muldner & Peter W. Steele, 1988 Addison-Wesley Publishing Co, Inc.,
pages 94-96. )).

Brent Burton ----------->  BPB9204@TAMVENUS   on BITnet