From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org
Subject: Re: screwy alist syntax
Date: Thu, 15 Apr 2004 21:10:18 -0400 [thread overview]
Message-ID: <m3wu4ghgmn.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <Pine.GSO.4.58.0404151606370.21948@marcy.nas.nasa.gov> (Brian S. McQueen's message of "Thu, 15 Apr 2004 16:11:35 -0700 (PDT)")
Brian S McQueen <bqueen@nas.nasa.gov> wrote:
> I just noticed something that looks screwy. Is there a good reason for
> the following?
Whether there was a good reason when these procedures were invented, I
can't say. (ass*-ref and other *-ref procedures follow the same
pattern among themselves, at least.) But backward compatibility is a
good reason now for them to stay the way they are.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-04-16 1:10 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 [this message]
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=m3wu4ghgmn.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--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).