Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!mnetor!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP
Newsgroups: net.lang.c
Subject: Re: Poorly terminated header files.
Message-ID: <2448@umcp-cs.UUCP>
Date: Wed, 16-Jul-86 22:20:00 EDT
Article-I.D.: umcp-cs.2448
Posted: Wed Jul 16 22:20:00 1986
Date-Received: Thu, 17-Jul-86 05:51:20 EDT
References: <5722@think.COM>
Reply-To: chris@maryland.UUCP (Chris Torek)
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 16

In article <5722@think.COM> rst@think.COM (Robert Thau) writes:
>What does X3J11 say about these cases, if anything?  The last time I
>looked at a draft standard, __LINE__ and __FILE__ were in it; what are
>their values on the split line, if such things are allowed?

`The last character in a source file included by a #include
preprocessing directive shall be a new-line character that is not
part of a token.'

I recall, but cannot find, a statement to the effect that an
unterminated line in an included file is essentially a syntax
error.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu