Message-ID: <352dc8d9.flying-brick@flying-brick.caverock.net.nz>
Date:      Fri, 10 Apr 1998 20:23:03 +1300
From: "Eric Gillespie (Root)" <root AT flying-brick DOT caverock DOT net DOT nz>
Organization: The Flying Brick computer
To: djgpp AT delorie DOT com
Subject:   Re: Newbie question: multiple #include statements
Precedence: bulk

In article <351C2E2B DOT 3637F2AE AT atlantis DOT stortek DOT com> Thomas Matthews writes:
(in comp.lang.c)
>Ion Ciordas-Ciurdariu wrote:
>> 
>> What happens if I include a file multiple times using several identical
>> #include <filename.h> statements ? Does the compiler include the file
>> only once or several times ? Should I try to avoid including more than
>> once ?
>> 
>> -calin

[snip]

> Some compilers may create an interim file consisting of
>tokens from multiple include files (more compact and efficient than
>parsing an ASCII file), for use by different source modules.  For
>example, if you have more than one ".c" file that includes "string.h",
>some compilers may precompile this header file.

A quick question - what support is there in gcc for this above mentioned idea?
And where would the gcc compiler store the pre-compiled headers?
Would the compilation be permanent, or only pre-compiled for each gcc session?

Thanks for answering this - though I suppose I could well have tried finding a
gnu.c group to ask this in...apologies, it's 22:05 and my eyelids are getting
a little too heavy.

Good night, and cheers from the Viking