unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Gregory Marton <gremio@csail.mit.edu>
Cc: bug-guile@gnu.org
Subject: Re: and-map and or-map not documented in the manual
Date: Wed, 08 Oct 2008 21:16:07 +0200	[thread overview]
Message-ID: <m3wsgij3t4.fsf@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810081215460.15470@samoa.csail.mit.edu> (Gregory Marton's message of "Wed, 8 Oct 2008 12:19:27 -0400 (EDT)")

Hey Gregory,

On Wed 08 Oct 2008 18:19, Gregory Marton <gremio@csail.mit.edu> writes:

> Hi Folks,
>
> A colleague just noticed that and-map and or-map, defined in boot-9.scm
> with some helpful comments above them, are not actually documented in
> the Guile Manual.  How might I go about adding them?

Good question. The thing is, they are the same as SRFI-1's `every' and
`any', which have a longer heritage; Common Lisp appears to call `any'
`some'.

I think the SRFI names are clearer[1], so you should use them. We have a
problem that we provide less general implementations[2] under strange
names[3].

So ideally instead of documenting them, if you're with me, we should
deprecate them, replacing them with their srfi-1 counterparts.

What do you think?

Andy

1. `and-map' implies that you can map syntax, which you cannot.
2. `and-map' doesn't handle multiple lists as `map' and `every' do.
3. I think only Chicken has and-map, and calls it `andmap'.
-- 
http://wingolog.org/




  reply	other threads:[~2008-10-08 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 16:19 and-map and or-map not documented in the manual Gregory Marton
2008-10-08 19:16 ` Andy Wingo [this message]
2008-10-09 15:54   ` Ludovic Courtès
2008-10-09 16:22     ` Gregory Marton
2008-10-10 10:08       ` Andy Wingo
2008-10-09 16:41     ` Sebastian Tennant

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=m3wsgij3t4.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=gremio@csail.mit.edu \
    /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).