From: Kenichi Handa <handa@ni.aist.go.jp>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: (aset UNIBYTE-STRING MULTIBYTE-CHAR)
Date: Wed, 13 Feb 2008 12:48:07 +0900 [thread overview]
Message-ID: <E1JP8bP-0004ZO-FJ@etlken.m17n.org> (raw)
In-Reply-To: <jwvir0t8tgm.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 12 Feb 2008 21:49:46 -0500)
In article <jwvir0t8tgm.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > Before the unicode merge, this worked:
> > (let ((str "a")) (aset str 0 (decode-char 'ucs #x100)))
> > In emacs-unicode-2 branch, there was a discussion about the
> > rightness of aset changing the multibyteness of a string,
> > and I changed the code to signal an error in the above case.
> An error sounds right.
For this:
(let ((str "\300")) (aset str 0 (decode-char 'ucs #x100)))
an error may be ok. But for the first example, although "a"
is currently treated as a unibyte string, I think it's more
like multibyteness-not-yet-decided, i.e. it's neutral about
the multibyteness.
> > But, I got reports claiming that the change breaks some of
> > already existing Elisp packages. Although changing the
> Details?
Something like this code:
(setq result (cons
(let ((str (make-string 1 0)))
(aset str 0 (make-char 'japanese-jisx0208 ku ten))
although it's easy to fix it...
> > What do you think is the right thing for this matter?
> aset on strings is fundamentally problematic, so anything that restricts
> it further is good in my book (my own local Emacs disallows them
> plainly, and I rarely bump into code that needs it).
What is the fundamental problem?
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-02-13 3:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 2:36 (aset UNIBYTE-STRING MULTIBYTE-CHAR) Kenichi Handa
2008-02-13 2:49 ` Stefan Monnier
2008-02-13 3:48 ` Kenichi Handa [this message]
2008-02-13 15:33 ` Stefan Monnier
2008-02-13 18:06 ` Stephen J. Turnbull
2008-02-13 19:33 ` Stefan Monnier
2008-02-13 22:49 ` Miles Bader
2008-02-14 1:11 ` Stephen J. Turnbull
2008-02-14 1:17 ` Miles Bader
2008-02-14 1:40 ` Stefan Monnier
2008-02-14 1:49 ` Miles Bader
2008-02-14 18:10 ` Richard Stallman
2008-02-14 22:40 ` David Kastrup
2008-02-15 1:08 ` Stephen J. Turnbull
2008-02-15 1:17 ` Miles Bader
2008-02-15 7:27 ` David Kastrup
2008-02-15 12:58 ` Richard Stallman
2008-02-14 23:37 ` Leo
2008-02-15 12:59 ` Richard Stallman
2008-02-14 4:20 ` Stephen J. Turnbull
2008-02-14 4:42 ` Richard Stallman
2008-02-15 1:39 ` Kenichi Handa
2008-02-15 4:27 ` Stefan Monnier
2008-02-15 8:42 ` Eli Zaretskii
2008-02-15 8:53 ` Miles Bader
2008-02-16 12:55 ` Eli Zaretskii
2008-02-16 5:53 ` Richard Stallman
2008-02-16 14:33 ` Stefan Monnier
2008-02-17 20:29 ` Richard Stallman
2008-02-18 1:15 ` Stefan Monnier
2008-02-18 4:00 ` Kenichi Handa
2008-02-18 17:31 ` Richard Stallman
2008-02-13 22:01 ` Richard Stallman
2008-02-13 23:13 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2008-04-15 7:11 Kenichi Handa
2008-04-15 15:52 ` Stefan Monnier
2008-04-17 1:13 ` Kenichi Handa
2008-05-07 19:31 Harald Hanche-Olsen
2008-05-14 6:54 ` Harald Hanche-Olsen
2008-05-14 12:22 ` Stefan Monnier
2008-05-14 12:50 ` Harald Hanche-Olsen
2008-05-15 1:18 ` Stefan Monnier
2008-05-15 6:11 ` Harald Hanche-Olsen
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=E1JP8bP-0004ZO-FJ@etlken.m17n.org \
--to=handa@ni.aist.go.jp \
--cc=emacs-devel@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.