On 08/06/2015 9:18 AM, Duncan Murdoch wrote: > On 08/06/2015 8:55 AM, Simon Urbanek wrote: >> Interesting - it seems to fail only the first time after the locale is set: >> >>> Sys.setlocale(locale="en_CA") >> [1] "en_CA/en_CA/en_CA/C/en_CA/en_US.UTF-8" >>> "320" > "300" >> [1] NA >>> "320" > "300" >> [1] TRUE >>> "320" > "300" >> [1] TRUE >> >> There is probably an associated error. I'll have a look later today unless >> someone beats me to it. > > I think I've got it, and should be able to commit a patch soon.
Committed as of revision 68489. Duncan > > Duncan > >> >> Thanks, >> Simon >> >> >> On Jun 8, 2015, at 7:40 AM, Duncan Murdoch <[email protected]> wrote: >> >>> I posted this to R-devel yesterday; from responses received, it appears >>> to be OSX-specific (maybe Mavericks-specific). >>> >>> In an R session started from the terminal with R --vanilla, I see this: >>> >>>> Sys.setlocale(locale="en_CA") >>> [1] "en_CA/en_CA/en_CA/C/en_CA/en_CA.UTF-8" >>>> "320" > "300" >>> [1] NA >>>> "320" > "300" >>> [1] TRUE >>> >>> The first string comparison after the locale change produces NA, while >>> later ones are fine. >>> >>> The locale string "en_CA" doesn't appear to matter, as long as it is >>> different from my previous locale. >>> >>> Do others see this? Can we fix it before the 3.2.1 release? >>> >>> Duncan Murdoch >>> >>> _______________________________________________ >>> R-SIG-Mac mailing list >>> [email protected] >>> https://stat.ethz.ch/mailman/listinfo/r-sig-mac >>> >> > _______________________________________________ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
