On 7/21/05, bear <xxxxxx@sonic.net> wrote:
>
> Finally, I suggest two additional functions:
>
> (set-current-locale! str)
[...]
> (current-locale)

These procedures are fine but I think all locale-specific procedures
should also take an optional locale argument which defaults to
(current-locale).  This is more general and is the natural way to do
things in a server or other multi-user environment where you are not
producing output for the current process' user, but for an arbitrary
locale associated with another entity.

--
Alex