[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 17:32:35 -0400

On Sat, Aug 27, 2016 at 16:00AM -0400, Claude Marinier wrote:
>> 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.

Windows 10 does not seem to have the concept of the "C" locale. I suspect
but cannot confirm that US_English may be equivalent to "C". Since I have
a working Chicken, I am inclined to leave it as is.

As more people start using Chicken on 64-bit Windows, we can address the
underlying problem.

On Sat, Aug 27, 2016 at 17:28PM -0400, Dan Leslie wrote:
> This is my Win64 locale:
> $ locale
> LANG=en_US.UTF-8
> LC_CTYPE="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"

Is that equivalent to "C" ?

Claude Marinier

reply via email to

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