From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Crashes with non-default language environments
Date: Mon, 11 Feb 2008 23:27:28 +0200 [thread overview]
Message-ID: <87ve4v9nk0.fsf@jurta.org> (raw)
In-Reply-To: <jwvk5lb4mmw.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 11 Feb 2008 09:06:01 -0500")
>>>>> 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.
Ah, sorry, since I've found no such function I assumed a typo.
I think adding a new function string-to-unibyte to complement
string-to-multibyte and other 2 multi->uni functions would be a good
thing for the short term even though all these names are confusing.
>> 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.
Since all those uni->multi/multi->uni functions have non-descriptive
names, using encode/decode-coding-string with explicit coding will
help writing more clean and less error-prone code. So I'd give a vote
for it.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-02-11 21:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 19:54 Crashes with non-default language environments Juri Linkov
2008-02-09 22:17 ` Juri Linkov
2008-02-10 2:09 ` Stefan Monnier
2008-02-10 22:48 ` Juri Linkov
2008-02-11 1:39 ` Stefan Monnier
2008-02-11 1:56 ` Miles Bader
2008-02-11 3:02 ` Stefan Monnier
2008-02-11 4:11 ` Miles Bader
2008-02-11 14:06 ` Stefan Monnier
2008-02-11 15:16 ` Miles Bader
2008-02-11 16:51 ` Stefan Monnier
2008-02-11 21:27 ` Juri Linkov [this message]
2008-02-12 11:41 ` Kenichi Handa
2008-02-12 16:29 ` Stefan Monnier
2008-06-25 2:58 ` bug#481: " Kenichi Handa
2008-06-25 3:49 ` bug#482: " Stefan Monnier
2008-07-02 10:44 ` bug#517: " Kenichi Handa
2008-07-03 22:23 ` bug#529: " Stefan Monnier
2008-07-04 2:27 ` bug#531: " Kenichi Handa
2008-02-12 11:23 ` Kenichi Handa
2008-02-12 19:29 ` Juri Linkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ve4v9nk0.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.