From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: John Cowan <cowan@ccil.org>
Cc: Mark H Weaver <mhw@netris.org>, guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: German translation of R5RS
Date: Fri, 1 Jun 2018 22:29:49 +0200 [thread overview]
Message-ID: <20180601202948.447xafwozut5rdlx@floriannotebook> (raw)
In-Reply-To: <CAD2gp_ROk6+mHHGXdJp7CEcKUxF=6UYdH3+Ha6xrXvx_8VZ3CA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Tue, May 29, 2018 at 06:58:35PM -0400, John Cowan wrote:
> 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.
>
That is good to know. I did a quick search for errata but did not
find any.
call-with-current-continuation is hard to fix. Redefinition of
keywords is not really an error. It is not clear to me if port?
should be part of R5RS or not.
In the German version I have changed begin to be syntax instead of
library syntax now. I also fixed list-ref.
https://pelzflorian.de/files/wip-r5rsde-patches-try-3.tar.gz
Regards,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-06-01 20:29 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
2018-06-01 20:29 ` pelzflorian (Florian Pelz) [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=20180601202948.447xafwozut5rdlx@floriannotebook \
--to=pelzflorian@pelzflorian.de \
--cc=cowan@ccil.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mhw@netris.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).