Am 08.06.2006 um 08:40 schrieb dda:
Actually, it doesn't change the line endings. I didn't thought it
would, and after trying it out, it sure doesn't... 0x0D, and then
0x0D0A stayed that way.
On 6/8/06, Jonathan Johnson <[EMAIL PROTECTED]> wrote:
/bin/sh -c "cat /foo/bar" > out.txt
Check to see if foo/bar and out.txt are the exact same. I'm guessing
that you'll notice that the line endings aren't the same anymore.
There are no reasons for Unix shells to do such transformations, and I
had always assumed that the lf > cr [on a Mac] conversions came from
RB. I'm still betting on it...
The only cases I know of, are when the a unix shell 'thinks' it is
talking to a terminal. In that case, certain shells or apps might change
something.
Typical call to shells using exec(), system() or whatever are supposed
to work transparently. Years ago I wrote a UNIX printer driver, which
used pipes heavily to transfer input stream through different binary
and textual filters. No problem. Not to speak of one compiler out of
several one I wrote, which used pipes to manage certain transformation
steps.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
