From: Andy Wingo <wingo@pobox.com>
To: Gregory Marton <gremio@csail.mit.edu>
Cc: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: and-map and or-map not documented in the manual
Date: Fri, 10 Oct 2008 12:08:11 +0200 [thread overview]
Message-ID: <m3hc7kiwz8.fsf@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810091158510.15470@samoa.csail.mit.edu> (Gregory Marton's message of "Thu, 9 Oct 2008 12:22:31 -0400 (EDT)")
Hi Gregory,
On Thu 09 Oct 2008 18:22, Gregory Marton <gremio@csail.mit.edu> writes:
> 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?
I apologize for hijacking your thread, it just reminded me of some
things I've been thinking about for a while. I think that documentation
would be great, as long as the docs suggest `every' for new code. A
patch to doc/ref/api-compound.texi in the "List Mapping" node would be
great.
That said, the fact that so many definitions are available in a normal
Guile session is a kind of problem -- it's useful but not very
orthogonal. On the other hand, as Ludovic mentioned, we don't want to
cause bitrot in old code, so we can't really change that interface.
I think that the proper solution to this is to finally allow Guile to
deal in other "languages", in the sense that mzscheme does. The default
language would be "guile", which corresponds to what we have now. We
could implement r6rs, which has a more orthogonal set of bindings. That
way we can e.g. have a session without all of the posix API visible from
the root module. It will be tricky but doable I think.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2008-10-10 10:08 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 [this message]
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=m3hc7kiwz8.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=gremio@csail.mit.edu \
--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).