On Thu, 2/28/19, Fritz Mueller via cctalk <cctalk@classiccmp.org> wrote:
> I've just been tripped up for a little
> over the fact that the C compiler barfs if there is
> whitespace/comentary before the first #include; the
>
> I found this curious.  Anybody
> know what the story is there?

My recollection is that it's documented in the 6th
Ed C manual that # has to be in the first column.
Beyond that, I vaguely recall something to the effect
that if the first line isn't a preprocessor directive,
then it skips any preprocessing at all.

BLS
 

Reply via email to