From: Brian S McQueen <bqueen@nas.nasa.gov>
Subject: screwy alist syntax
Date: Thu, 15 Apr 2004 16:11:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0404151606370.21948@marcy.nas.nasa.gov> (raw)
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
assv key alist
assoc key alist
scm_assq (key, alist)
scm_assv (key, alist)
scm_assoc (key, alist)
BUT the assq-ref func take an alist and a key, which is the opposite
order:
assq-ref alist key
assv-ref alist key
assoc-ref alist key
scm_assq_ref (alist, key)
scm_assv_ref (alist, key)
scm_assoc_ref (alist, key)
I think these should two classes of functions should have their args in
the same order.
Brian McQueen
NAS Division
NASA/Ames
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2004-04-15 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 23:11 Brian S McQueen [this message]
2004-04-16 1:10 ` screwy alist syntax Paul Jarc
2004-04-16 21:04 ` Stephen Compall
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=Pine.GSO.4.58.0404151606370.21948@marcy.nas.nasa.gov \
--to=bqueen@nas.nasa.gov \
/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).