Problem with @eval[sin(0)] and similar

Feb 1, 2010
15
0
#1
Hello,

Unless I'm wrong, the following issue has not been reported yet. Did I mistyped something?
D:\X>echo %@eval[sin(0)]
Eval warning: '_set_string', Non-digit char found in parse
Eval warning: Text =
Eval warning: 0.000000000000000000000000000000,
0

D:\X>echo %@eval[cos(0)]
8000000000000000000000000000000

D:\X>echo %@eval[tan(0)]
Eval warning: '_set_string', Non-digit char found in parse
Eval warning: Text =
Eval warning: 0.000000000000000000000000000000,
0

D:\X>echo %@eval[tan(pi)]
Eval warning: '_set_string', Non-digit char found in parse
Eval warning: Text =
Eval warning: -0.409295251930604372057504812992,
0

D:\X>echo %@eval[tan(3,141592654)]
Eval warning: '_set_string', Non-digit char found in parse
Eval warning: Text =
Eval warning: 0.000000000410206761537356616744,
0

D:\X>echo %@eval[log(2)]
Eval warning: '_set_string', Non-digit char found in parse
Eval warning: Text =
Eval warning: 0.693147180559945309417232121458,
0

D:\X>echo %@eval[log10(2)]
Eval warning: '_set_string', Non-digit char found in parse
Eval warning: Text =
Eval warning: 0.301029995663981195213738894725,
0
etc...

Working under XP Pro (French) and the last TCC 11.0 build 50. It seems the same problem exists since TCC 9 or even before...

Any idea?
Esteban
 
#2
and similar

This does not happen when the DecimalChar is Period and the ThousandsChar is
Comma. When reversed (as in your setup, I believe from the 3,141... below)
the problem shows up.

To test the other way, use option / Advanced / Localization.

On Wed, Jun 30, 2010 at 6:56 AM, Esteban <> wrote:


> Hello,
>
> Unless I'm wrong, the following issue has not been reported yet. Did I
> mistyped something?D:\X>echo %@eval[sin(0)]
> Eval warning: '_set_string', Non-digit char found in parse
> Eval warning: Text > Eval warning: 0.000000000000000000000000000000,
> 0
>
> D:\X>echo %@eval[cos(0)]
> 8000000000000000000000000000000
>
> D:\X>echo %@eval[tan(0)]
> Eval warning: '_set_string', Non-digit char found in parse
> Eval warning: Text > Eval warning: 0.000000000000000000000000000000,
> 0
>
> D:\X>echo %@eval[tan(pi)]
> Eval warning: '_set_string', Non-digit char found in parse
> Eval warning: Text > Eval warning: -0.409295251930604372057504812992,
> 0
>
> D:\X>echo %@eval[tan(3,141592654)]
> Eval warning: '_set_string', Non-digit char found in parse
> Eval warning: Text > Eval warning: 0.000000000410206761537356616744,
> 0
>
> D:\X>echo %@eval[log(2)]
> Eval warning: '_set_string', Non-digit char found in parse
> Eval warning: Text > Eval warning: 0.693147180559945309417232121458,
> 0
>
> D:\X>echo %@eval[log10(2)]
> Eval warning: '_set_string', Non-digit char found in parse
> Eval warning: Text > Eval warning: 0.301029995663981195213738894725,
> 0
>
> etc...
>
> Working under XP Pro (French) and the last TCC 11.0 build 50. It seems the
> same problem exists since TCC 9 or even before...
>
> Any idea?
> Esteban
>
>
>
>
>


--
Jim Cook
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.
 
Feb 1, 2010
15
0
#3
Re: and similar

This does not happen when the DecimalChar is Period and the ThousandsChar is Comma. When reversed (as in your setup, I believe from the 3,141... below) the problem shows up.

To test the other way, use option / Advanced / Localization.
Hi,

You're right, the localization was set on Automatic, i.e. comma for decimal separator in France. Strange enough, even things like %@eval[pi] shows weird results but without error message.

Until this issue is fixed, I'll use setdos /g., in my batches only for calculations.

Thanks Jim
 

rconn

Administrator
Staff member
May 14, 2008
10,533
94
#4
Re: and similar

> You're right, the localization was set on Automatic, i.e. comma for
> decimal separator in France. Strange enough, even things like
> %@eval[pi] shows weird results but without error message.
>
> Hope this will be corrected one day.
It's fixed in 11.0.51 (already uploaded).

Rex Conn
JP Software
 
G

Glennbo51

Guest
#5
Re: and similar

On 07/01/2010 08:52, rconn wrote:

> ---Quote---
>> You're right, the localization was set on Automatic, i.e. comma for
>> decimal separator in France. Strange enough, even things like
>> %@eval[pi] shows weird results but without error message.
>>
>> Hope this will be corrected one day.
> ---End Quote---
> It's fixed in 11.0.51 (already uploaded).
>
> Rex Conn
> JP Software
>
>
>
>
>
Check for updates doesn't find it yet
 
G

Glennbo51

Guest
#6
Re: and similar

On 07/01/2010 10:02, GlennBo51 wrote:

> On 07/01/2010 08:52, rconn wrote:
>
>
> ---Quote---
>> ---Quote---
>>> You're right, the localization was set on Automatic, i.e. comma for
>>> decimal separator in France. Strange enough, even things like
>>> %@eval[pi] shows weird results but without error message.
>>>
>>> Hope this will be corrected one day.
>> ---End Quote---
>> It's fixed in 11.0.51 (already uploaded).
>>
>> Rex Conn
>> JP Software
>>
>>
>>
>>
>>
> ---End Quote---
> Check for updates doesn't find it yet
>
>
>
>
>
My mistake I was in the wrong place. It did update. My Bad