> > I didn't put UTF-8 in on purpose, because I'd just as soon not deal with it
> > internally. Variable length character data's a pain in the butt, and if we
> > can avoid having the internals deal with it except as a source that gets
> > converted to UTF-32, that's fine with me.
>
> I agree with Branden that a default 4x memory bloat would not be popular.
>
> > The native and foreign string data types were an attempt to accommodate
> > UTF-8, as well as ASCII and EBCDIC character data. One of the three will
> > likely be the native type, and the rest will be foreign strings. I'm not
> > sure if perl should have only one foreign string type, or if we should have
> > a type tag along with the other bits for strings.
>
> Umm, one way or another I suspect UTF-8 will be in there.
I suspect so too but very grudgingly. As Dan said dealing with
variable length data is a major pain. UTF-8 is certainly a much
better designed VLD than most but it's still a pain.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
