Dan Sugalski <[EMAIL PROTECTED]> doodled:
> At 11:09 PM 3/23/2001 +0000, Simon Cozens wrote:
> >For instance, chr() will produce Unicode codepoints. But you can pretend that
> >they're ASCII codepoints, it's only the EBCDIC folk that'll get hurt. I hope
> >and suspect there'll be an equivalent of "use bytes" which makes chr(256)
> >either blow up or wrap around.
>
> Actually no it won't. If the string you're doing a chr on is tagged as
> EBCDIC, you'll get the EBCDIC value. Yes, it does mean that this:
>
> chr($foo) == chr($bar);
>
> could evaluate to false if one of the strings is EBCDIC and the other
> isn't.
Err, perhaps I'm being dumb here - but surely $foo and $bar arent
typed strings, they're just numbers (or strings which match /^\d+$/) ???
