Path: utzoo!attcan!uunet!ssbell!mcmi!amperif!unocss!ho@fergvax.unl.edu From: ho@fergvax.unl.edu (Michael Ho) Newsgroups: comp.sys.ibm.pc Subject: Re: Trouble compiling flip with TurboC 1.5 Message-ID: <1139@unocss.UUCP> Date: 26 Jul 89 15:14:25 GMT References: <8760@attctc.Dallas.TX.US> Sender: news@unocss.UUCP Reply-To: ho@fergvax.unl.edu Lines: 24 From article <8760@attctc.Dallas.TX.US>, by ltf@attctc.Dallas.TX.US (Lance Franklin): > In article <55868@tut.cis.ohio-state.edu> Christopher Schanck writes: > 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. :-) Actually, it *is* signal now. In Turbo C 2.0. Confused yet? :-) Seriously, if someone is gonna post a program to transport something across architectures, they should give you a file readable on the TARGET machine, not the source machine -- and moaning about how the target machine SHOULD have read files of this type is ridiculous. (After all, if we REALLY expected the target PC to read LF-only lines, then this entire program was unneccessary.) P'raps I should write a Mac program to convert Mac files to PC files... then sell it to unwitting PC owners. Same issue, isn't it? --- ... Michael Ho, University of Nebraska