[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#22910: read-only setlocale has side effect

From: Zefram
Subject: bug#22910: read-only setlocale has side effect
Date: Fri, 4 Mar 2016 16:48:59 +0000

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) (write (port-encoding (current-input-port))) (newline)'

Observe that this occurs even if the locale reading operation is for a
category unrelated to character encoding.  The actual decoding behaviour
of read-char is altered in accordance with the reported encoding.
Non-primordial ports opened before or after the setlocale call are
not affected.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]