Perhaps this is not related to the locale problem. That one shows itself
when a call to strtod in the code in otran.c (constndx()) fails and the
error message issued is "Error: numeric syntax...".

It can also happen in score lines and RT events (I've seen 'too many 
pfields'
pop up when it does).

In any case, we need to look at all the strtod calls and see what can be
done to ensure they work.

Victor
----- Original Message ----- 
From: "Jean-Pierre Lemoine" 
To: 
Sent: Monday, March 17, 2008 9:47 PM
Subject: [Csnd] Re: 5.08 java and setLocale - more


> This is so strange that I tried to remove "asiglo clip asigl, 2, 
> 31622.764" from the generated file. It is then correctly compiled by the 
> csound api.
> "asiglo clip asigl, 2, 31622" gives an error on clip opcode (invalid 
> opcode)
>
> I have many numerical values in the orc , and they are correctly 
> interpreted.
>
> jp
>> The following error
>> error:  illegal character ., line 309:
>> asiglo clip asigl, 2, 31622.764
>>                           ^
>> was suggested to be corrected by using
>>
>> setlocale(LC_ALL, "C");
>> before the call to Compile()
>>
>> I have no idea on how to set this from a java host using the csound api. 
>> I have tried  " Locale.setDefault( Locale.ENGLISH );"  without any 
>> success.
>> Thanks for any help, and why is this now required? new parser?
>>
>> jp
>>
>>
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>>
>>
>>
>
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"