Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!tut.cis.ohio-state.edu!harmonica.cis.ohio-state.edu!schanck
From: schanck@harmonica.cis.ohio-state.edu (Christopher Schanck)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Trouble compiling flip with TurboC 1.5
Message-ID: <55868@tut.cis.ohio-state.edu>
Date: 24 Jul 89 14:38:27 GMT
References: <26514@agate.BERKELEY.EDU> <1105@unocss.UUCP> <26586@agate.BERKELEY.EDU> <5608@pt.cs.cmu.edu> <1325@mks.UUCP>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Christopher Schanck <schanck@cis.ohio-state.edu>
Organization: Ohio State University Computer and Information Science
Lines: 22

In article <1325@mks.UUCP> alex@mks.waterloo.edu (Alex White) writes:
>In article <5608@pt.cs.cmu.edu> ralf@b.gp.cs.cmu.edu (Ralf Brown) writes:
>>TC 2.0 *almost* works with LF-only lines.  Seems that only the preprocessor
>>command-recognizer fails.... (i.e. an #ifdef will get you a complaint about
>>a missing #endif, but a file without conditional compilation compiles
>>correctly).  I do agree that this is an annoying problem.  Unless I
>>misremember, TC 1.5 was the same as 2.0.

Not to be a pain, but in what situation is this a problem?  If you are
compiling source generated elsewhere (Unix system, for example), why
not crank it through a filter to fix things?  Such a filter should be
trivial to write, yes?  If your editor is generating these files,
well, then you have more of a problem, but still solvable by switching
editors.  

But somehow I get the feeling I missed something...

Chris
-=-
"This town needs an enema."
                    ---- Joker, "Batman"
Christopher Schanck (schanck@cis.ohio-state.edu)