From: Neil Jerram <neil@ossau.uklinux.net>
To: "Luigi Semenzato" <luigi@semenzato.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-user@gnu.org
Subject: Re: bug in read?
Date: Tue, 30 Oct 2007 23:52:24 +0000 [thread overview]
Message-ID: <87odegrwhz.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <c6bf18db0709250922u65536de0n434722c720245186@mail.gmail.com> (Luigi Semenzato's message of "Tue, 25 Sep 2007 09:22:19 -0700")
"Luigi Semenzato" <luigi@semenzato.com> writes:
> Thank you for the explanation.
>
> Does anybody know then why the Guile manual replicates
> sections of r5rs instead of just pointing to them?
> It's redundant and it leads to this kind of problems.
>
> If Guile is Scheme version blah with some additions and
> some omissions, shouldn't the manual just document
> the additions and the omissions?
Perhaps, yes. But there is also the view that it is helpful for the
manual to try to be a complete guide for "how to use Guile", without
relying on indirection to other material. I don't think the argument
is as one-sided as you suggest.
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-10-30 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 17:29 bug in read? dsmich
2007-09-25 16:22 ` Luigi Semenzato
2007-10-30 23:52 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-17 21:49 Luigi Semenzato
2007-09-23 15:54 ` Andy Wingo
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=87odegrwhz.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
--cc=luigi@semenzato.com \
--cc=wingo@pobox.com \
/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).