Say what!? (Re: MSC 5.0 Bug Fix?? (Simple..))

Daniel R. Levy levy at ttrdc.UUCP
Sat Feb 20 11:27:15 AEST 1988


In article <1988Feb17.171813.15472 at utzoo.uucp>, henry at utzoo.uucp (Henry Spencer) writes:
> > Compiler  apparently does not like eof markers that are at the end of
> > the last line in a file.  Error c1004 results. Putting a cr-lf at the
> > end of the file solved the problem.
> 
> Compiler is doing it right, although the complaint is perhaps undesirably
> cryptic.  X3J11:  "A source file that is not empty shall end in a new-line
> character."  (Page 6, line 38, 11 Jan 1988 draft)

Ahem, what does X3J11 have to say about source files on systems (like VMess)
that support "record" text files?  There need be no new line character in them,
but each record ("line") in the file is defined by some other mechanism,
e.g., a byte count prepended to each record.  (Of course the answer should be
that such source files are treated for the purpose of the standard as if they
ended with a newline character, but is this actually an explicit part of the
standard?  And if not, shouldn't it be?  And for that matter, what if, in
the middle of a record in such a file, an actual newline character is found?
How is the compiler supposed to treat that??)
-- 
|------------Dan Levy------------|  Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
|         an Engihacker @        |  	<most AT&T machines>}!ttrdc!ttrda!levy
| AT&T Computer Systems Division |  Disclaimer?  Huh?  What disclaimer???
|--------Skokie, Illinois--------|



More information about the Comp.lang.c mailing list