Re: [MacPerl-Modules] Re: Need authoritative Apple refs for EOL == CR

["Paul J. Schinder" <schinder@pobox.com>]

On Tue, Mar 02, 1999 at 10:57:49AM -0400, Arved Sandstrom wrote:
} 
} Most of the Perl+XML guys aren't this anal. They're actually trying to
} usefully implement XML. But this discussion went over into the realm of
} "Is XML flawed?", there's a few straight-XML types involved, and like I
} say, I have a hunch that *they* will ultimately want paper. That's
} assuming that they don't just ignore the whole problem.

OK, now I understand the problem.  (The best thing to do with
bureaucrats is to ignore them if you can, but you can't.)  It'd help
if *Apple* would get it right; did you look at the TechNote mentioned
this morning?  I'm not interested enough to dig into my Java book and
see if \n is hardwired to \012 in the Java spec (p.s. well, ok.  I
did.  It is.  That's nuts.  No wonder they need a println.)  . But if
it isn't, then Apple fouls up again, since the TN assumed it was.

You know the relevant section of the ISO C standard, right?  Matthias
posted it to the list a long time ago (so long ago that it may be in
Sandra Silcot's archive).  As I recall, it says that \n is a platform
dependent symbol for end-of-line straight out, and is not a hard wired
constant.  I don't know of a reference offhand, but if you can find
it, that would seem to me to be a show stopper.  (Precedence by
another official committee and all that.)  Then ask them to consider
how portable code itself would be if \n were a hardwired constant but
EOL differed (as they are beginning to realise, it sounds like).

} 
} Arved
} 
} 
} 
} 

-- 
Paul Schinder
schinder@pobox.com

==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-modules-request@macperl.org