From: <tomas@tuxteam.de>
To: 38398@debbugs.gnu.org
Subject: bug#38398: non-obvious SCM_EOF_VAL rationale
Date: Wed, 27 Nov 2019 13:34:04 +0100 [thread overview]
Message-ID: <20191127123404.GE30482@tuxteam.de> (raw)
In-Reply-To: <20191127120534.i6okeasqcaodpae6@fysh.org>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
On Wed, Nov 27, 2019 at 12:05:34PM +0000, Zefram via Bug reports for GUILE, GNU's Ubiquitous Extension Language wrote:
[...]
> But please don't get sidetracked. This wasn't a feature request for
> "#eof" [...]
To be fair, you contributed strongly to this side-tracking. By waving
a big red flag:
"This poor design precludes RnRS specifying read syntax for any
EOF object [...]"
you yourself drew attention to the underlying issues of the design
instead of keeping things focused to the documentation.
I agree that the doc could improve in this case...
Cheers
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2019-11-27 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 7:44 bug#38398: non-obvious SCM_EOF_VAL rationale Zefram via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2019-11-27 8:55 ` John Cowan
2019-11-27 12:05 ` Zefram via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2019-11-27 12:34 ` tomas [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=20191127123404.GE30482@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=38398@debbugs.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).