bug#38398: non-obvious SCM_EOF_VAL rationale

2019-11-27 Thread tomas
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

bug#38398: non-obvious SCM_EOF_VAL rationale

2019-11-27 Thread Bug reports for GUILE, GNU's Ubiquitous Extension Language
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

bug#38388: [2.9.5] Inaccurate source location info for unbound variables

2019-11-27 Thread Andy Wingo
Hi, On Tue 26 Nov 2019 16:20, Ludovic Courtès writes: > I have a test that runs ‘guix system build’ on this file: > > (use-modules (gnu)) ; 1 > (use-service-modules networking) ; 2 > > (operating-system ;

bug#38398: non-obvious SCM_EOF_VAL rationale

2019-11-27 Thread John Cowan
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