From: Stephen Compall <s11@member.fsf.org>
Cc: guile-user@gnu.org
Subject: Re: screwy alist syntax
Date: 16 Apr 2004 16:04:53 -0500 [thread overview]
Message-ID: <xfyisfztz0q.fsf@csserver.evansville.edu> (raw)
In-Reply-To: <Pine.GSO.4.58.0404151606370.21948@marcy.nas.nasa.gov>
Brian S McQueen <bqueen@nas.nasa.gov> writes:
> I just noticed something that looks screwy. Is there a good reason for
> the following?
>
> The assq func take a key and an alist:
>
> assq key alist
> ...
> BUT the assq-ref func take an alist and a key, which is the opposite
> order:
>
> assq-ref alist key
> ...
Just making up stuff here, but I think that `assq' et al are historic
Lisp functions, and so were left as they were. However, `assq-ref' et
al are new, so can have the `right' order. They aren't in Emacs,
anyway.
--
Stephen Compall or s11 or sirian
Most people's favorite way to end a game is by winning.
Mena monarchist AFSPC analyzer arrangements quarter Ft. Bragg
MILSATCOM BRLO Consul Reno kilo class Europol JFK Roswell
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-04-16 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 23:11 screwy alist syntax Brian S McQueen
2004-04-16 1:10 ` Paul Jarc
2004-04-16 21:04 ` Stephen Compall [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xfyisfztz0q.fsf@csserver.evansville.edu \
--to=s11@member.fsf.org \
--cc=guile-user@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.
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).