From: Kenichi Handa <handa@m17n.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: request for a new function, say, `sequence'
Date: Wed, 26 Mar 2003 09:18:58 +0900 (JST) [thread overview]
Message-ID: <200303260018.JAA08092@etlken.m17n.org> (raw)
In-Reply-To: <24784.1048623017@theforce.Stanford.EDU> (satyakid@stanford.edu)
In article <24784.1048623017@theforce.Stanford.EDU>, "Satyaki Das" <satyakid@stanford.edu> writes:
>> >> (defun dev-charseq (from &optional to)
>> >> (if (null to) (setq to from))
>> >> (mapcar (function (lambda (x) (indian-glyph-char x 'devanagari)))
>> >> (devanagari-range from to)))
>>
>> > (defun dev-charseq (lower &optional upper)
>> > (if (null upper) (setq upper lower))
>> > (loop for x from lower to upper
>> > collect (indian-glyph-char x 'devanagiri)))
>>
>> It's not the point. How to use a list returned by `range'
>> (or `sequence') and how to make such a list is a different
>> thing.
> I am trying to show that by using existing macros and functions we
> can express the algorithms as clearly and succintly as with the
> new `range'.
In your example code, you united the implementaion of range
and usage of the returned list. In such a way, of course,
it is natural that we can make a function that uses `range'
more concise and efficient.
> Do you have a counter-example to this?
How about the code something like this.
(defvar dev-consonants
(append (range (decode-char 'ucs #x0915) (decode-char 'ucs #x0939))
(range (decode-char 'ucs #x0958) (decode-char 'ucs #x095F))))
(defun dev-looking-at-syllable ()
(and (memq (following-char) dev-consonants)
(looking-at dev-syllable-pattern)))
The first `memq' is to avoid the heavy `looking-at' in an
unnecessary case.
The defvar part can be written as:
(defvar dev-consonants
(append (loop for x from (decode-char 'ucs #x0915) to (decode-char 'ucs #x0939)
collect x)
(loop for x from (decode-char 'ucs #x0958) to (decode-char 'ucs #x095F)
collect x)))
but using `range' is much more handy and easier to read.
> IMO, a new builtin function is needed if and only if it makes
> writing code easier or makes it simpler.
I'm not requesting a builtin function. And, `range' surely
makes writing code easier and makes the code simpler as well
as dolist, dotimes, while, and etc. do.
> I think calling the new function `sequence' or `range' is a
> mistake. Lisp already has the functions `string' and `vector'
> which are data type constructors. Either of the suggested names
> sound like a new data type (in fact there is already a data type
> called sequence and a predicate sequencep) and so inconsistent
> with the current naming conventions.
I see your point.
> So I suggest that a more descriptive name be chosen -- for
> instance something like `make-sequence-of-numbers'.
I don't insist on having TYPE argument, always returning a
list is ok. So, for instance, make-number-list, is also
acceptable.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-03-26 0: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 [this message]
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=200303260018.JAA08092@etlken.m17n.org \
--to=handa@m17n.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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.