Re: Crashes with non-default language environments

[Kenichi Handa <handa@ni.aist.go.jp>]

In article <jwvir0wci47.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

>>> 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.

But, even if we implement string-to-unibyte, it should be
used for a string containing only ascii and eight-bit chars.
And in that case, string-make-unibyte behaves exactly the
same as string-to-unibyte.

Miles Bader <miles@gnu.org> writes:
[...]
> Ok, perhaps
> `vector-to-raw-string-whose-bytes-in-memory-should-have-exactly-the-same-values-as-the-elements-of-this-vector'.

We now have
`list-to-raw-string-whose-bytes-in-memory-should-have-exactly-the-same-values-as-the-elements-of-this-list';
that is `unibyte-string'

---
Kenichi Handa
handa@ni.aist.go.jp