At 03:02 AM 10/23/2001 -0400, James Mastros wrote:
>I don't see what chr() should look like, though. What's the interface to
>multiple encodings on the opcode level? I'd like to just say that chr
>always creates a utf32 string.
Nope, can't do that.
>String encodings don't have fixed numbers in
>a plugable-encoding world (and I assume that's where we're going), so I
>can't take an i|ic parameter for that. String encodings are an enum, so I
>can't take the name of the encoding as an s|sc parameter. Ideas?
There'll be a few predefined string encodings. Probably encoding 0 will be
native, 1 will be UTF-32. Beyond that you need to look it up by name and
cache the encoding offset.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
