unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Sebastian Tennant <sebyte@smolny.plus.com>
To: bug-guile@gnu.org
Subject: Re: and-map and or-map not documented in the manual
Date: Thu, 09 Oct 2008 16:41:53 +0000	[thread overview]
Message-ID: <ej2psotq.fsf@vps203.linuxvps.org> (raw)
In-Reply-To: 87zlldu5kl.fsf@gnu.org

Quoth ludo@gnu.org (Ludovic Courtès):
> Andy Wingo <wingo@pobox.com> writes:
>
>> So ideally instead of documenting them, if you're with me, we should
>> deprecate them, replacing them with their srfi-1 counterparts.
>
> I'm with you, but I think the status quo is safer, so that code from the
> late 90's can run forever with Guile (hmm, how convincing is that?).

How about deprecating them in the documentation only.

Dare I say that if it exists, it should be documented, (if only to
direct the user elsewhere).

Something like this maybe:

  -- Scheme Procedure: and-map pred lst1 lst2 ... lstN

  Please see <info-xref to 'every'>.

  Note: The reason for having two procedures that do the same thing is
        primarily historical. 'and-map' only exists in Guile whereas
        'every' can be found in most (if not all) Scheme
        implementations.  It will not be removed (for the sake of
        backwards compatiblity) but there's no reason to use it unless
        you want your code to be non-portable.

Seb


 





      parent reply	other threads:[~2008-10-09 16:41 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
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 [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=ej2psotq.fsf@vps203.linuxvps.org \
    --to=sebyte@smolny.plus.com \
    --cc=bug-guile@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).