Re: Compilation problems??

In article <m3iuwn1ny5.fsf_at_unknown.localdomain>

           M.A.Brown-4_at_sms.ed.ac.uk "Mark Brown" writes:

>phaywood_at_aardvark.apana.org.au.STOP.SPAM (Peter "Shaggy" Haywood) writes:
>
>> Groovy hepcat Programming was jivin' on Mon, 11 Aug 1997 10:12:13
>> -0500 in comp.lang.c.
>> Compilation problems??'s a cool scene! Dig it!
 

>> >#include "stdio.h"
 

>> First, stdio.h should be enclosed in angle brackets, not quotes. It
>> is a standard header file, not a header you've written. Also, I would
>
>This will, however, work. "" will eventually search in the same
>places as <> - but your suggestion is much better practice.

It *might* work. The problem is that the "" form might find a file called stdio.h before ut searches like the <> form. The standard doesn't guarantee anything about the end results of:

#include "stdio.h"

but it does guarantee:

#include <stdio.h>

...

>He *needs* to include stdlib.h - he's called exit() and (more
>importantly) malloc(), which means he should include the appropriate
>header file.

Just header, there's no stipulation that they be files! :-)

-- 
-----------------------------------------
Lawrence Kirby | fred_at_genesis.demon.co.uk
Wilts, England | 70734.126_at_compuserve.com
-----------------------------------------