[RFC] Merge charsets and encodings

[Andrew Whitworth]

I think we're very quickly going to get into a tarpit of bickering
over the names "encoding" and "charset". I think that the core of the
proposal here isn't to ignore one or the other, or to drop all
"encodings" in favor of only allowing changable "charsets" or
whatever.

The core of the proposal is that each string doesn't need two pointers
to controlling structures. We especially don't need them if they tend
to boil down to a small handful of specific combinations. We can
instead have a single pointer to a single "string manager" object
which will do the work that separate "encodings" and "charsets" do
currently.

--Andrew Whitworth



On Wed, Aug 25, 2010 at 9:25 AM, NotFound <julian.notfound at gmail.com> wrote:
>> ...in other words, you're proposing that Parrot declare that it will
>> never use any character sets other than Unicode?  What about ebcdic,
>> iso-8859-*, KOI8-*, etc?
>
> Not at all. They all can be worked as encodings.
>
> --
> Salu2
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>