Re: Crashes with non-default language environments

[Stefan Monnier <monnier@iro.umontreal.ca>]

>>>> Of course, string-AS-unibyte is the worst of all three.  But nobody
>>>> suggested to use that one.  I just suggested to replace
>>>> string-MAKE-uniybte by string-TO-unibyte.
>> 
>>> Where's this string-to-unibyte function?  My emacs doesn't have it...
>> 
>> Oh, that's right, we still don't have it.  We only have the 3 variants
>> on the uni->multi, but not on the multi->uni.
>> I guess now is a good time to introduce it.

> I find the names of all these function incredibly confusing though...

Agreed.

> What's really wanted here, is something like
> vector-to-raw-string-dont-you-dare-do-any-encoding, right?
> [As the bytecode engine wants raw bytes with the same numbers, which
> just happened to be inside a string]

The problem is that "no encoding" means different things to
different people.  At some point I proposed to just throw out all those
functions, and force people to use encode/decode-coding-string instead,
which forces them to think a bit about what they're doing.

Oh, and throw away the `no-conversion' coding-system, of course, since
it has the same problem.


        Stefan