Re: RFC 69 (v3) Standardize input record separator (for

>>>>> "PRL" == Perl6 RFC Librarian <[email protected]> writes:

PRL> =head1 ABSTRACT

PRL> The default input record separator is not safe for all input files
PRL> on all platforms.  There should also be support for Unicode line
PRL> separator (U+2028) and paragraph separator (U+2029).

You want to add, "non-native text files" somewhere in there.

PRL> =head1 DESCRIPTION

PRL> The input record separator should match the platform's C compiler
PRL> mappings of "\r\n" (CRLF), "\n" (LF) and "\r" (CR), which are often
PRL> (but not always, e.g., EBCDIC-based platforms [Peter Prymmer]):

What does this mean? I can't make out what you are trying to say.

PRL>     000D 000A
PRL>     000A
PRL>     000D

This are not the line seperators on my platform. If this were in
a file, I would not consider it a text file. You have embeded nuls
in there.

PRL> For Unicode-capable platforms, the input record separator should
PRL> also match:

PRL>     2028
PRL>     2029

What does unicode-capable platform mean? It should depend upon the
file I'm reading not on the capablities of the os.

PRL> Given this input file:

PRL>     D O S CR LF    0044 004F 0053 000D 000A
PRL>     U n i x  LF    0055 006E 0069 0078 000A
PRL>     M a c CR       004D 0061 0063 000D
PRL>     l i n e  LS    006C 0069 006E 0065 2028
PRL>     p a r a  PS    0070 0061 0072 0061 2029
PRL>     l i n e        006C 0069 006E 0065

Same problem. I don't have embedded nuls in any of my text files.


<chaim>
-- 
Chaim Frenkel					     Nonlinear Knowledge, Inc.
[email protected]				               +1-718-236-0183