IRC channel logs
2026-07-01.log
back to list of logs
<old>rlb: what was tha spec you mentioned ? #u8".." <rlb>"info guile srfi-207" :) (new) <rlb>(new to guile I mean) <rlb>Though in 3.0 it has to be read-enabled. <old>ahh I see that's cool <old>hmm is it me or spawn is just broken in the REPL due to readline changing stdin to a soft port <rlb>I don't know if we'd want to, but I suppose we could consider enabling bytestrings by default in some future release. Or we might want some other way to have "per-module file" reader options. iirc the reader changes are global, so if you try have a .scm file with a module that uses some non-default options (like bytestrings or prefix keywords or...) that'll break modules loaded later. <rlb>And no solid idea what "per-module file" (or per-module/file) or... would actually mean. <old>yes having reader global is kind of weird <rlb>I suppose for the common case some kind of "read-enable/disable-until-eof" might work: (define-module (foo) ...) (read-enable-until-eof 'bytestrings) ... <rlb>But that's not quite right either I suspect. <rlb>I think I'd want it to affect the forms in the (define-module ...) file and any code loaded from that, but not any sub-modules loaded.