[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [MiNT] Here documents and CRLF



> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Andreas Schwab
> Sent: Friday, June 18, 1999 11:27 AM
> To: reschke@muenster.de
> Cc: Andreas Schwab; Guido Flohr; MiNT mailing list
> Subject: Re: [MiNT] Here documents and CRLF
>
>
> "Julian Reschke" <reschke@muenster.de> writes:
>
> |> > From: Andreas Schwab [mailto:schwab@issan.cs.uni-dortmund.de]
> |> > Sent: Friday, June 18, 1999 10:53 AM
> |> > To: reschke@muenster.de
> |> > Cc: Guido Flohr; MiNT mailing list
> |> > Subject: Re: [MiNT] Here documents and CRLF
> |> >
> |> >
> |> > "Julian Reschke" <reschke@muenster.de> writes:
> |> >
> |> > |> Keep in mind that the standard line delimiter for TOS
> systems can't be
> |> > |> changed just by saying "we want it the UNIX way". There are
> |> > lots of sources
> |> > |> of text information on a TOS system, and except for some ports
> |> > of UNIX tools
> |> > |> these files always will have CR/LF (not to speak of text
> files that you
> |> > |> might have copied from -- gasp -- a DOS/Windows system).
> |> >
> |> > But if you set 'b' in UNIXMODE you tell MiNTlib that your
> system is POSIX
> |> > compliant in this area, so your get what you deserve if it is not.
> |> >
> |> > If all you care is POSIX then "r" and "rb" are one and the same.
> |>
> |> However then stdin and stdout are treated as binary, which
> they aren't (in
> |> most cases).
>
> In POSIX text == binary.  Your system is POSIX.  You are done.

Well, my system certainly is not POSIX. For instance, I have text files with
CR/LF :-).