From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: request for a new function, say, `sequence'
Date: Wed, 26 Mar 2003 21:18:47 +0900 (JST) [thread overview]
Message-ID: <200303261218.VAA09242@etlken.m17n.org> (raw)
In-Reply-To: <jk4r5qwm20.fsf@glug.org> (message from Thien-Thi Nguyen on 26 Mar 2003 03:48:23 -0500)
In article <jk4r5qwm20.fsf@glug.org>, Thien-Thi Nguyen <ttn@glug.org> writes:
> "Edward O'Connor" <ted@oconnor.cx> writes:
> I believe this is called `range' in Python, which perhaps lends
> something (else) to that name over using `sequence'.
> as far as name preferences, my 2c: `iota'.
Richard suggested `sequential-list' which, I think, is also
a good name. And as far as he suggested it, I think he
admitted to install than function. So, I'll install it this
weekend if there aren't any more strong objections.
By the way, `iota' and Python's `range' are slightly
different from what I want. I think we should avoid to have
a function of the same name but slightly different from that
of the other language unless there's a strong reason.
range(10) => [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
range(5, 10) => [5, 6, 7, 8, 9]
range(0, 10, 3) => [0, 3, 6, 9]
range(-10, -100, -30) => [-10, -40, -70]
If range is used on simple numbers, this spec is not bad.
But, I'd like to use it also for character codes and glyph
codes as below:
(sequential-list ?a ?z) => (?a ?b ... ?z)
It seems strange to write
(sequential-list ?a ?{)
or
(sequential-list ?a (1+ ?z))
to get (?a ?b ... ?z).
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-03-26 12:18 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303261218.VAA09242@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).