[m-dev.] Porposal: Support reading/writing either dos/unix file endings on any platform

Paul Bone paul at bone.id.au
Tue Nov 12 14:30:31 AEDT 2013

On Tue, Nov 12, 2013 at 01:03:10PM +1100, Peter Wang wrote:
> > 
> > Thoughts?
> I think you should specify whether you want CRLF->LF translation for
> input streams, and LF->CRLF for output streams (defaulting to, e.g.
> "yes" for input and "host" for output).  I'm not keen on the automatic
> detection.  If it's limited to checking if/what type of newline
> translation was required in the input stream *so far* then that's
> probably ok.  output_stream_line_ending_style seems pointless.

The automatic detection is useful when the programmer doesn't care which
format is used, but wants to provide a consistency for the user.  This is
true for the 'error' program.

Regarding CRLF->LF translation for input streams.  Are you saying that when
a programmer reads from an input streams that, as a programmer, they should
only have to expect LF characters?  Is this too unix centric?  I haven't
done programming on windows for a very long time, what would a windows
programmer expect?

> A related problem is file encodings, and the "UTF-8 BOM".

Yep, I'm no expert here.

Paul Bone

More information about the developers mailing list