From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: request for a new function, say, `sequence'
Date: Tue, 25 Mar 2003 10:25:18 +0900 (JST) [thread overview]
Message-ID: <200303250125.KAA06703@etlken.m17n.org> (raw)
In-Reply-To: <200303250057.h2P0vBj6016367@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)
In article <200303250057.h2P0vBj6016367@rum.cs.yale.edu>, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
>> (dolist (c (sequence #X #Y 'list))
>> ..operate-on-C)
> I agree that such code is pretty common, but I'd rather extend dotimes
> to allow something like (dotimes (c (cons X Y)) BODY).
I'm not sure it is a good idea to extend dotimes and make it
different from Commong Lisp. And, using `sequence' is more
flexible, for instance, in the following case.
;; Combining diacritics
(setq c #x300)
(while (<= c #x362)
(modify-category-entry (decode-char 'ucs c) ?^)
(setq c (1+ c)))
;; Combining marks
(setq c #x20d0)
(while (<= c #x20e3)
(modify-category-entry (decode-char 'ucs c) ?^)
(setq c (1+ c)))
can be:
(dolist (c (append (sequence #x0300 #x0362 'list)
(sequence #x20d0 #x20e3 'list)))
(modify-category-entry (decode-char 'ucs c) ?^)
Of course, in this specific case, allowing FROM and TO in
modify-category-entry is better.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-03-25 1:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 3:02 request for a new function, say, `sequence' Kenichi Handa
2003-03-24 15:41 ` Stefan Monnier
2003-03-25 0:15 ` Kenichi Handa
2003-03-25 0:50 ` Kenichi Handa
2003-03-25 0:57 ` Stefan Monnier
2003-03-25 1:25 ` Kenichi Handa [this message]
2003-03-25 1:47 ` Luc Teirlinck
2003-03-25 1:51 ` Luc Teirlinck
2003-03-25 1:59 ` Kenichi Handa
2003-03-25 2:29 ` Luc Teirlinck
2003-03-25 1:57 ` Satyaki Das
2003-03-25 2:08 ` Kenichi Handa
2003-03-25 2:41 ` Satyaki Das
2003-03-25 4:46 ` Kenichi Handa
2003-03-25 5:05 ` Satyaki Das
2003-03-25 5:40 ` Kenichi Handa
2003-03-25 20:10 ` Satyaki Das
2003-03-26 0:18 ` Kenichi Handa
2003-03-26 1:44 ` Satyaki Das
2003-03-26 2:38 ` Luc Teirlinck
2003-03-26 7:31 ` Edward O'Connor
2003-03-26 8:48 ` Thien-Thi Nguyen
2003-03-26 12:18 ` Kenichi Handa
2003-03-27 3:30 ` Richard Stallman
2003-04-03 2:54 ` Kenichi Handa
2003-04-03 3:44 ` Miles Bader
2003-04-03 22:52 ` Richard Stallman
2003-04-03 10:41 ` Thien-Thi Nguyen
2003-04-04 2:11 ` Vinicius Jose Latorre
2003-04-04 22:23 ` Richard Stallman
2003-04-05 2:10 ` Vinicius Jose Latorre
2003-04-06 2:00 ` Richard Stallman
2003-04-08 8:10 ` Kenichi Handa
2003-04-03 22:52 ` Richard Stallman
2003-03-25 15:27 ` Stefan Monnier
2003-03-25 23:11 ` Kenichi Handa
2003-03-26 0:11 ` Miles Bader
2003-03-26 0:40 ` Luc Teirlinck
2003-03-26 1:34 ` Miles Bader
2003-03-26 0:54 ` Kenichi Handa
2003-03-26 1:29 ` Miles Bader
2003-03-26 15:44 ` Stefan Monnier
2003-03-27 0:09 ` Luc Teirlinck
2003-03-27 15:20 ` Stefan Monnier
2003-03-27 15:53 ` Luc Teirlinck
2003-03-27 16:06 ` Stefan Monnier
2003-03-27 17:03 ` Luc Teirlinck
2003-03-27 17:08 ` Stefan Monnier
2003-03-26 2:41 ` Richard Stallman
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=200303250125.KAA06703@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
/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.