[Top][All Lists]

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

Re: [Chicken-hackers] Windows 10, MinGW-W64, Chicken 4.11, "invalid enco

From: Claude Marinier
Subject: Re: [Chicken-hackers] Windows 10, MinGW-W64, Chicken 4.11, "invalid encoded numeric literal"
Date: Sat, 27 Aug 2016 16:00:30 -0400

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.
> >
> >
> >
> >
> > 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:
> 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.

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.


Claude Marinier

reply via email to

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