From: jdominy AT saturn DOT cs DOT unp DOT ac DOT za (James Dominy)
Newsgroups: comp.os.msdos.djgpp
Subject: #include satements necessary?
Date: 1 Sep 1998 08:26:51 GMT
Organization: CS and IS, Univ of Natal, PMB
Lines: 27
Message-ID: <904638408.433550@mars.cs.unp.ac.za>
NNTP-Posting-Host: raven.und.ac.za
Cache-Post-Path: mars.cs.unp.ac.za!jdominy AT saturn DOT cs DOT unp DOT ac DOT za
Cache-Post-Path: Raven!news AT mars DOT cs DOT unp DOT ac DOT za
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

First of all, sorry but I can't find a threading/posting option in my news
reader, so I had to post this as a sparate message. It is in reply to the
original message with the same subject.

With regards to the 'automatic' including of files by rhide, no RHIDE does
not as far as I know add the '#include' statements. Rather it links the
entire c statard library into your program, so the functions you use are
there for the linker to find when it needs them, even without the include
statements. What you probably will find, is that instead of errors when
compiling you will get a series of warnings of the vain -

 Warning : implicit declaration of function xxxxx()

What this means, if there are no errors, is that the compiler leaves those
functions which are given as warnings with some sort of flag in the .o file
it creates, which the linker that acts upon to resolve a final address for
the function. If you were to leave out an include for one of your own
files/libraries, the linker would not find the funtion in the c statndard
libraries, and would spew out an error to join the warning.

Hope this helps, and as a hint for knowing 'everythin' that is wrong, always
compile and link the project/file you are writing separately to running it.
This way you will get to see the warnings before the screen switches to your
program output.

Cheers
James