Re: [Chicken-hackers] Windows 10, MinGW-W64, Chicken 4.11, "invalid encoded numeric literal"

[Dan Leslie]

This is my Win64 locale:

$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_ALL=

-Dan


On 2016-08-27 1:00 PM, Claude Marinier wrote:
> On Sat, Aug 27, 2016 at 11:03AM -0400, Peter Bex wrote:
> > On Sat, Aug 27, 2016 at 11:08:20AM -0400, Claude Marinier wrote:
> > > We have seen this before but these may not be related.
> > >   https://github.com/nickg/swank-chicken/issues/10
> > >
> > >
> http://nongnu.13855.n7.nabble.com/quot-panic-invalid-encoded-numeric-literal-quot-with-gtk-td196533.html
> > >
> > > The other interesting question is: Why me?
> >
> > I asked Hugo on IRC if he ever figured out why he got this error, and
> > it turns out that CHICKEN has a bug in that its numeric parser relies
> > on C functions to convert strings to numbers, which means it's locale-
> > sensitive.  It shouldn't do that (because string->number isn't defined
> > to be locale-sensitive in the Scheme spec).
> >
> > See:
> https://gist.github.com/hugoArregui/7b5626c7dc00f45cdb4ea8721db4f777
> >
> > Can you check your locale environment variables, and see if resetting
> > it to the "C" locale works around the bug?
>
> Hi Peter,
>
> The locale is "English_Canada.1252".
>
> So if Dan Leslie's environment has a locale of "C", that may explain why
> it works for him.
>
> http://lists.nongnu.org/archive/html/chicken-users/2016-08/msg00011.html
>
> If I can find a way to temporarily set the locale from the command prompt,
> I can bracket the build with a pair to switch to "C" and back.
> Otherwise, I
> will have to use the Control Panel. I shall experiment.
>
> Thanks.
>
> -- 
> Claude Marinier

signature.asc
Description: OpenPGP digital signature