From: Gregory Marton <gremio@csail.mit.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: and-map and or-map not documented in the manual
Date: Thu, 9 Oct 2008 12:22:31 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0810091158510.15470@samoa.csail.mit.edu> (raw)
In-Reply-To: <87zlldu5kl.fsf@gnu.org>
From a user's perspective, reading code containing these functions, it can
be confusing that they're undocumented and not defined in the user portion
of the code. Either deprecating them or documenting them with the caveats
mentioned would be better than the status quo.
I would prefer to document them, because it's less work, and because the
pointer into srfi-1 would help new users find other tools they might need.
Can I be helpful in making that happen?
Thanks,
Grem
> Hi,
>
> 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?).
>
> Thanks,
> Ludo'.
>
>
>
>
--
------ __@ Gregory A. Marton http://csail.mit.edu/~gremio/
--- _`\<,_ .
-- (*)/ (*) Confidence is the feeling you have until you understand.
~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~++~~~~~~~
next prev parent reply other threads:[~2008-10-09 16:22 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 [this message]
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=Pine.LNX.4.64.0810091158510.15470@samoa.csail.mit.edu \
--to=gremio@csail.mit.edu \
--cc=bug-guile@gnu.org \
--cc=ludo@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).