bug#24186: setlocale can't be localised

Ludovic Courtes wrote: >That wouldn't help with the "setlocale" issue you describe per se, but >this would address such use cases in a different way. > >WDYT? Yes, explicit locale objects and locale parameters to relevant functions are a good thing. In general, the model of a global locale state

bug#24186: setlocale can't be localised

Hi, Zefram skribis: > (define (call-with-locale cat val body) > (let ((oldval #f)) > (dynamic-wind > (lambda () (set! oldval (setlocale cat)) (setlocale cat val)) > body (lambda () (setlocale cat oldval) > > (define (day-of-week-string) >

bug#24186: setlocale can't be localised

On Tue 09 Aug 2016 14:15, Zefram writes: > I wrote: >>is my first time compiling a Guile myself. It's failing on a missing >>library for which Debian supplies no package. > > Turns out there was a package. It was complaining about a lack of > "bdw-gc", and Debian doesn't have

bug#24186: setlocale can't be localised

I wrote: >is my first time compiling a Guile myself. It's failing on a missing >library for which Debian supplies no package. Turns out there was a package. It was complaining about a lack of "bdw-gc", and Debian doesn't have anything of that name, but it does have it under the name "libgc".

bug#24186: setlocale can't be localised

Greets :) Firstly, just to make sure that we are getting things right in 2.2 (and if not we need to know), would you mind testing with the latest 2.1.x release? Also, do you have a concrete program whose behavior you expect to be different? I appreciate the call-with-locale example but I'm not

bug#24186: setlocale can't be localised

In Guile 1.8 it was possible to localise the effect of a setlocale operation, but in Guile 2.0 it's no longer possible by natural use of the locale API. This loss of a useful facility is either a bug or something that needs to be discussed in the documentation. In Guile 1.8 one could perform a