At 10:48 PM 3/23/2001 +0000, Simon Cozens wrote:
>On Thu, Mar 22, 2001 at 04:10:28PM -0500, Dan Sugalski wrote:
> > Yes, I realize that point 5 may result in someone getting a meaningless
> > Unicode string. Too bad--it is *not* the place of a programming
> language to
> > enforce validity on data. That's the programmer's job.
>
>But points 4 and 5 do enforce Unicode on everyone. Not that I'm particularly
>upset by that idea, but... :)
Nah, they only apply to data that perl's tagged as Unicode, either because
its input stream is marked that way or because the program explicitly
converted the data. A plain:
open FOO, "some.file";
while (<FOO>) { whatever($_)}
probably won't be dealing with Unicode data. (Unless for some reason perl's
been told that all files are Unicode by default)
I expect the default data types for data that comes from files will be
either binary or ascii for most systems, EBCDIC on OS/390 systems, and
potentially Unicode on Windows and non-US systems.
Dealing with typed strings might make binmode (and perhaps corresponding
asciimode, unicodemode, or ebcdicmode) more frequently used. Or not.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
