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... :) open FH, $datafile or die $!; undef $/; $foo = <FH>; die "Confusing" if -s $datafile != length $foo; I'm just not sure it's fair on Old World hackers. Will there be a way to stop Perl upgrading stuff to Unicode on the way in? -- <pudge> i've dreamed in Perl many time, last night i dreamed in Make, and that just sucks.
- Re: Unicode handling Dan Sugalski
- Re: Unicode handling Nicholas Clark
- Re: Unicode handling Dan Sugalski
- RE: Unicode handling NeonEdge
- RE: Unicode handling Dan Sugalski
- Re: Unicode handling Damien Neil
- Re: Unicode handling Dan Sugalski
- Re: Unicode handling Dave Storrs
- Re: Unicode handling Dan Sugalski
- Re: Unicode handling nick
- Re: Unicode handling Simon Cozens
- Re: Unicode handling Dan Sugalski
- Re: Unicode handling Simon Cozens
- Re: Unicode handling Brad Hughes
- Re: Unicode handling Simon Cozens
- Re: Unicode handling Dan Sugalski
- Re: Unicode handling Damien Neil
- RE: Unicode handling Garrett Goebel
- RE: Unicode handling Dan Sugalski
- Re: Unicode handling Dave Mitchell
- Re: Unicode handling Dan Sugalski