From: Kevin Ryde <user42@zip.com.au>
Subject: doco srfi-1 alist-delete
Date: Tue, 26 Aug 2003 08:00:08 +1000 [thread overview]
Message-ID: <87y8xhcs9j.fsf@zip.com.au> (raw)
* srfi-modules.texi (SRFI-1 Association Lists): In alist-delete and
alist-delete!, note argument order in the equality calls, per SRFI-1
spec.
- Scheme Procedure: alist-delete key alist [=]
- Scheme Procedure: alist-delete! key alist [=]
Return a list containing the elements of ALIST but with those
elements whose keys are equal to KEY deleted. The returned
elements will be in the same order as they were in ALIST.
Equality is determined by the = predicate, or `equal?' if not
given. The order in which elements are tested is unspecified, but
each equality call is made `(= key alistkey)', ie. the given KEY
parameter is first and the key from ALIST second. This means for
instance all associations with a key greater than 5 can be removed
with `(alist-delete 5 alist <)'.
`alist-delete' does not modify ALIST, but the return might share a
common tail with ALIST. `alist-delete!' may modify the list
structure of ALIST to construct its return.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-08-25 22:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y8xhcs9j.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).