From: John Cowan <cowan@ccil.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Mark H Weaver <mhw@netris.org>, guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: German translation of R5RS
Date: Tue, 29 May 2018 18:58:35 -0400 [thread overview]
Message-ID: <CAD2gp_ROk6+mHHGXdJp7CEcKUxF=6UYdH3+Ha6xrXvx_8VZ3CA@mail.gmail.com> (raw)
In-Reply-To: <20180529170324.cj6rtan2ukcd36nn@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
On Tue, May 29, 2018 at 1:03 PM, pelzflorian (Florian Pelz) <
pelzflorian@pelzflorian.de> wrote:
> English R5RS has two errors that I know of. Eq? is claimed to return
> “true or false”, but the examples make clear it is #t or #f. In the
> specification of with-output-to-file a THUNK argument is referred to
> as PROC. Should such (minor) errors be fixed? One of my patches also
> fixes a misplaced space character in the Texinfo.
>
http://mumble.net/~kelsey/r5rs-errata.html are the semi-official errata.
IMO you should incorporate them.
--
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
The Penguin shall hunt and devour all that is crufty, gnarly and
bogacious; all code which wriggles like spaghetti, or is infested with
blighting creatures, or is bound by grave and perilous Licences shall it
capture. And in capturing shall it replicate, and in replicating shall
it document, and in documentation shall it bring freedom, serenity and
most cool froodiness to the earth and all who code therein. --Gospel of Tux
[-- Attachment #2: Type: text/html, Size: 1696 bytes --]
next prev parent reply other threads:[~2018-05-29 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180428184817.3jbux62427sfhdjn@floriannotebook>
[not found] ` <20180502184924.ypvspfxay3vyj2o3@floriannotebook>
2018-05-12 23:44 ` German translation of R5RS pelzflorian (Florian Pelz)
2018-05-29 16:08 ` Mark H Weaver
2018-05-29 16:17 ` Freja Nordsiek
2018-05-29 17:03 ` pelzflorian (Florian Pelz)
2018-05-29 22:58 ` John Cowan [this message]
2018-06-01 20:29 ` pelzflorian (Florian Pelz)
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='CAD2gp_ROk6+mHHGXdJp7CEcKUxF=6UYdH3+Ha6xrXvx_8VZ3CA@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
--cc=pelzflorian@pelzflorian.de \
/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).