On Wed, Nov 27, 2019 at 12:05:34PM +, 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
John Cowan wrote:
>On the contrary: the EOF object is not a character, but it *can* be
>returned by read-char .
Bother. Of course I meant "can't be returned by read-char in a non-EOF
situation". I was alluding precisely to it being distinguishable from
characters for the purposes of that return
On Wed, Nov 27, 2019 at 2:45 AM Zefram via Bug reports for GUILE, GNU's
Ubiquitous Extension Language wrote:
> It's fairly obvious
> that it's a value that can't be returned by read-char, and therefore is
> not itself a character, but that's quite a different matter.
On the contrary: the EOF
The part of the Guile manual on the representation of immediate objects
says:
# -- Macro: SCM SCM_EOF_VAL
# The Scheme end-of-file value. It has no standard written
# representation, for obvious reasons.
I disagree with the manual: the reasons for the EOF value having no
s-expression rep
