Re: RFC 131 (v1) Internal String Storage to be Opaque

2000-08-18 Thread Jarkko Hietaniemi
That's the thing. It doesn't matter. It Bshouldn't matter. Keep it pluggable; you could have everything in Latin1, in UTF8, in UTF16, or who knows what, but the core developer shouldn't have to care. One good way to achieve this is to have the string presented in the variable as an array of

Re: RFC 131 (v1) Internal String Storage to be Opaque

2000-08-18 Thread Larry Wall
Simon Cozens writes: : On Fri, Aug 18, 2000 at 09:57:59AM -0700, Larry Wall wrote: : Because we don't lose much efficiency to polymorphism, since we need it : anyway to support generic scalars, and we gain some efficiency whenever : we procrastinate conversions out of existence. : : Surely we