From: Justin Sheehy <justin@linus.mitre.org>
Subject: Re: cl
Date: 27 Jan 1999 16:01:50 -0500 [thread overview]
Message-ID: <glm679s77lt.fsf@caffeine.mitre.org> (raw)
In-Reply-To: Jan Vroonhof's message of "27 Jan 1999 20:10:49 +0100"
Jan Vroonhof <vroonhof@math.ethz.ch> writes:
> Wouldn't it have been much nicer if the map syntax had been
>
> (mapc list func) so you could just write the nice and pure
>
> (mapc some-thing
> (lambda (var)
> ....))
What's wrong with the current mapc syntax? Is there something that
you would like other than to have the parameter order reversed?
-Justin, confused
next prev parent reply other threads:[~1999-01-27 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-27 17:03 cl Lars Magne Ingebrigtsen
1999-01-27 19:10 ` cl Jan Vroonhof
1999-01-27 21:01 ` Justin Sheehy [this message]
1999-01-28 7:37 ` cl Lars Magne Ingebrigtsen
1999-01-28 18:16 ` cl Hrvoje Niksic
1999-12-14 4:21 cl Katsumi Yamaoka
1999-12-14 11:01 ` cl Hrvoje Niksic
1999-12-14 11:37 ` cl Katsumi Yamaoka
1999-12-14 18:55 ` cl Jan Vroonhof
1999-12-14 22:43 ` cl Katsumi Yamaoka
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=glm679s77lt.fsf@caffeine.mitre.org \
--to=justin@linus.mitre.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.
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 NNTP newsgroup(s).