At 11:16 AM 8/5/00 +0000, Nick Ing-Simmons wrote: >Benjamin Stuhl <[EMAIL PROTECTED]> writes: > >It has also led to the perl5 internals being, to put it > >bluntly, a horrible mess. > >Agreed - but that is due to grafting it in late - and possibly >trying to be too clever intuiting whether existing perl5-code is >working on bytes or chars. I'm tempted to just say "utf-8 *everywhere*", but that's got the whole binary data problem. Bleah. I think, unfortunately, the language folks need to hammer out the semantics before we can get the details worked on. :( Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl Simon Cozens
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl Bart Schuller
- Re: RFC: Foreign objects in perl Simon Cozens
- Re: RFC: Foreign objects in perl Nick Ing-Simmons
- Re: RFC: Foreign objects in perl Benjamin Stuhl
- Char encoding Nick Ing-Simmons
- Re: Char encoding Bryan C . Warnock
- Re: Char encoding Nick Ing-Simmons
- Re: Char encoding Dan Sugalski
- Re: Char encoding Simon Cozens
- Re: Char encoding Dan Sugalski
- Re: Char encoding Simon Cozens
- Re: Char encoding Jarkko Hietaniemi
- Re: Char encoding Simon Cozens
- Re: Char encoding Dan Sugalski
- Re: Char encoding Larry Wall
- Re: Char encoding Dan Sugalski
- Re: Char encoding Larry Wall
- Re: Char encoding Larry Wall