From: "Satyaki Das" <satyakid@stanford.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: request for a new function, say, `sequence'
Date: Mon, 24 Mar 2003 18:41:23 -0800 [thread overview]
Message-ID: <1191.1048560083@theforce.Stanford.EDU> (raw)
In-Reply-To: <200303250208.LAA06802@etlken.m17n.org>
Kenichi Handa <handa@m17n.org> writes:
> In article <32627.1048557446@theforce.Stanford.EDU>, "Satyaki Das" <satyakid@stanford.edu> writes:
>
> > If I were you I would be using loop as follows:
>
> > ;; Combining diacritics
> > (loop for c from #x300 to #x362
> > do (modify-category-entry (decode-char 'ucs c) ?^))
>
> > Is there any particular reason for loop to be avoided? It is a
> > macro in CL, so it gets expanded at compile time. I ask since I
> > have used it in MH-E.
>
> The above is an example usage of `sequence' (or `range'),
> not the reason of requesting this function. The original
> reason is that there are cases that we need a list generated
> by this function.
The examples in this thread have all created a list (or vector)
and then iterated over the elements. The loop macro is ideal for
this (and more efficient since it doesn't cons up a list -- though
efficiency shouldn't be an issue). That is why I suggested this.
Are there lots of places where just a list of ascending numbers
needs to be returned?
> And, as far as I remember, it should be avoided to require
> `cl' in a preloaded file if possible. Is this rule changed
> now?
Using `loop' requires cl at compile time only. So adding the
following line is sufficient:
(eval-when-compile (require 'cl))
If the preloaded file is compiled then 'cl isn't actually loaded
at run time.
Satyaki
next prev parent reply other threads:[~2003-03-25 2:41 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 [this message]
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=1191.1048560083@theforce.Stanford.EDU \
--to=satyakid@stanford.edu \
--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.