Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!attctc!ltf
From: ltf@attctc.Dallas.TX.US (Lance Franklin)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Trouble compiling flip with TurboC 1.5
Message-ID: <8760@attctc.Dallas.TX.US>
Date: 25 Jul 89 08:58:11 GMT
References: <26514@agate.BERKELEY.EDU> <1105@unocss.UUCP> <26586@agate.BERKELEY.EDU> <5608@pt.cs.cmu.edu> <1325@mks.UUCP> <55868@tut.cis.ohio-state.edu>
Reply-To: ltf@attctc.Dallas.TX.US (Lance Franklin)
Organization: The Unix(R) Connection BBS, Dallas, Tx
Lines: 23

In article <55868@tut.cis.ohio-state.edu> Christopher Schanck <schanck@cis.ohio-state.edu> writes:
>>TC 2.0 *almost* works with LF-only lines.  Seems that only the preprocessor
>>command-recognizer fails....
>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? 

Which brings us full circle...the program flip, mentioned in the Subject
line, does that very thing...converts a Unix-style LF-only file into an
MS-DOS-style CR-LF file (or visa-versa).

Which means we have now entered an endless loop!  did somebody remember to
do a signal(SIGINT...) so we can ctrl-c out of this thread?

Oh, I forgot...it's ssignal, isn't it.   :-)

Lance

-- 
+-------------------------+ +------------------------------------------+
| Lance T Franklin        | | "And all who heard should see them there,
| ltf@attctc.DALLAS.TX.US | |  And all should cry, Beware!  Beware!
+-------------------------+ +  His flashing eyes, his floating hair!"