🚀 go-pugleaf

In article <33978@grapevine.uucp> koreth (Steven Grimm) writes:
^In article <2829@tahoe.unr.edu^ mikew@wheeler.UUCP (Mike Whitbeck) writes:
^^HELP ! 
^^I seem to get extra \r's from putchar()!!!! (or getchar()?)
^
^On the ST, the end-of-line code is \r\n, not just \n as it is on UNIX.
^In order to output valid text files, C libraries translate \n to \r\n
^on output, and back the other way on input.
^
^Most C compilers on the ST let you pass a "b" modifier to in the second
^parameter of fopen(); this tells the compiler to skip its I/O translation.
^ ...
^Hope that helps.
^
^sgrimm@sun.com		...!sun!sgrimm

Actually I am not getting the \r\n pair just the \r and somewhat
randomly sprinkled throughout the file.

A la UN*X I planned to use the splay program as a filter using
stdin and stdout. Maybe I can write a scratch file fopen'd as
per your sugesstion and then cat the scratch file to stdout via
Pexec or execvec().

Thanks for the reply.