Xref: utzoo comp.sources.d:4070 comp.sys.ibm.pc:34955
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!pt.cs.cmu.edu!b.gp.cs.cmu.edu!ralf
From: ralf@b.gp.cs.cmu.edu (Ralf Brown)
Newsgroups: comp.sources.d,comp.sys.ibm.pc
Subject: Re: Problems compiling Gnuplot w/ TC 2.0
Keywords: linking, error, Gnuplot, TC 2.0
Message-ID: <6195@pt.cs.cmu.edu>
Date: 19 Sep 89 22:09:29 GMT
References: <1077@lakesys.UUCP> <25879@iuvax.cs.indiana.edu> <497@proton.UUCP>
Distribution: usa
Organization: Carnegie-Mellon University, CS/RI
Lines: 21

In article <497@proton.UUCP> baumann@muon.UUCP (Michael Baumann) writes:
}>I've been bitten by this a few times, and it's rally frosting me.
}>What's happening is that TC2.0 (unlike previous versions) no longer
}>accepts lines that are delimited by ^J only --- it demands ^M^J.  By
}
}1) How TC2.0 handles  ^J or ^J^M verses TC1.5 should be a moot point.
}   No where in the definition of the C language are new-lines (however
}   you want to make 'em) defined as required for ANY statement. They are
}   WHITE SPACE. To be consumed by the Lexical Analyzer. They should 
}   Never be seen by the parser.

The parser doesn't care, but the preprocessor chokes on ^J-only files when
processing conditionals.  Try compiling a file with no #ifdef, #ifndef, or
#if.  It will compile properly.


-- 
{backbone}!cs.cmu.edu!ralf   ARPA: RALF@CS.CMU.EDU   FIDO: Ralf Brown 1:129/46
BITnet: RALF%CS.CMU.EDU@CMUCCVMA   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER? |"Humor is laughing at what you haven't got when you ought to
What's that?| have it."  -- Langston Hughes