From: MON KEY <monkey@sandpframing.com>
To: handa@m17n.org
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: raw-byte and char-table
Date: Wed, 25 Aug 2010 22:58:22 -0400 [thread overview]
Message-ID: <AANLkTinaF1Z2Rvp_sDv-ciHNjY4=eoW7e46KS3_yN-Hh@mail.gmail.com> (raw)
> Number like #x3FFFA0 is so criptic. The function name
> unibyte-char-to-multibyte is also not ideal, but I think
> it's better than #x3FFFA0.
Maybe I am misunderstanding, but I think the `#x' and `#o' syntax is
not cryptic at all in the context. These at least preserve identity:
4194208, #o17777640, #x3fffa0
This signals an error:
(unibyte-char-to-multibyte
(unibyte-char-to-multibyte 160))
Also, there is the brevity factor:
(aref (syntax-table) #o17777640)
(aref (syntax-table) #x3fffa0)
(aref (syntax-table) 4194208)
(aref (syntax-table)
(unibyte-char-to-multibyte 160))
> We could provide a ?\NNN (or similar) notation for it. Similarly to
> what we do for those bytes in multibyte strings.
Howsabout just this one for all of them:
`#\'
:)
> Stefan
--
/s_P\
next reply other threads:[~2010-08-26 2:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 2:58 MON KEY [this message]
2010-08-26 3:34 ` raw-byte and char-table Kenichi Handa
2010-08-26 5:30 ` MON KEY
2010-08-26 6:48 ` Kenichi Handa
2010-08-26 7:09 ` Miles Bader
2010-08-27 3:30 ` MON KEY
2010-08-27 3:45 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2010-08-24 1:11 Kenichi Handa
2010-08-24 3:06 ` Eli Zaretskii
2010-08-24 4:29 ` Kenichi Handa
2010-08-24 17:08 ` Eli Zaretskii
2010-08-25 4:05 ` Kenichi Handa
2010-08-26 0:01 ` Stefan Monnier
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='AANLkTinaF1Z2Rvp_sDv-ciHNjY4=eoW7e46KS3_yN-Hh@mail.gmail.com' \
--to=monkey@sandpframing.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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.