> SRFI-6 (string ports) says nothing about port encodings, and yet
> portable code written for SRFI-6 will fail on Guile 2.0 unless the
> string is constrained to whatever the default port encoding happens to
> be. This is not just a theoretical issue; it has caused trouble in
> practice, e.g.:
Hey, there’s a patch for SRFI-6 there. Could we resume the discussion
in that bug?
Guile ports are mixed textual/binary ports. Whether this or separate
binary/textual ports as in R6 is best is an interesting question, but as
you note, we cannot really change that currently.