On Fri 04 Mar 2016 17:48, Zefram writes:
> A call to setlocale with no second argument is documented to be
> a read-only operation, querying the current locale configuration.
> In fact it has a side effect of setting the encoding on primordial ports:
This sounds like a bug indeed :/
Andy
Additional information: setlocale's side effect on primordial ports
happens even if the port's encoding has been individually set using
set-port-encoding!. This means that to maintain a specific encoding on
these ports (other than the locale's nominal encoding, which is likely to
not be binary com
A call to setlocale with no second argument is documented to be
a read-only operation, querying the current locale configuration.
In fact it has a side effect of setting the encoding on primordial ports:
$ guile-2.0 -c '(write (port-encoding (current-input-port))) (newline)
(setlocale LC_TIME) (w
