I can verify that the same thing happens OS X. If I had to make a
guess, the line counter in Csound starts at 0, where as our text
editor starts counting lines at 1.

Best,
Jake
-- 
The Csound Blog - http://csound.noisepages.com/


On Mon, Dec 7, 2009 at 7:08 AM, Rene Djack  wrote:
> Hi list,
>
> Here is an old problem i have with csound on linux.
>
> I don't have the correct error line number,
> same result if i add --csd-line-nums=1 in the command line.
>
> 
> 
> -Wfd -+rtaudio=null -+rtmidi=null --expression-opt
> 
> 
> sr           = 44100
> ksmps    = 1
>
> instr 1
> asig      ascil    10000, 110, 1        ;error oscil and not ascil, on csd
> line 10
>             out       asig
> endin
> 
> 
> f 1    0    8193    10    1
> i 1    0    1
> 
> 
>
> output from csound is:
> orch compiler:
> 7 lines read
>     instr    1
> error:  no legal opcode, line 16:
> asig    osciil    10000, 110, 1
> error:  input arg 'asig' used before defined, line 17:
>     out    asig
> 2 syntax errors in orchestra.  compilation invalid
>
> Cheers,
> René
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi,

It wouldn't depend on the editor as this value is generated by Csound
alone. I've noticed some of this behavior with macros or  labels, not
sure which. Maybe in this case it has to do with CsOptions content?

Cheers,
Andrés

On Tue, Dec 8, 2009 at 5:20 PM, Jacob Joaquin  wrote:
> I can verify that the same thing happens OS X. If I had to make a
> guess, the line counter in Csound starts at 0, where as our text
> editor starts counting lines at 1.
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
>
>
> On Mon, Dec 7, 2009 at 7:08 AM, Rene Djack  wrote:
>> Hi list,
>>
>> Here is an old problem i have with csound on linux.
>>
>> I don't have the correct error line number,
>> same result if i add --csd-line-nums=1 in the command line.
>>
>> 
>> 
>> -Wfd -+rtaudio=null -+rtmidi=null --expression-opt
>> 
>> 
>> sr           = 44100
>> ksmps    = 1
>>
>> instr 1
>> asig      ascil    10000, 110, 1        ;error oscil and not ascil, on csd
>> line 10
>>             out       asig
>> endin
>> 
>> 
>> f 1    0    8193    10    1
>> i 1    0    1
>> 
>> 
>>
>> output from csound is:
>> orch compiler:
>> 7 lines read
>>     instr    1
>> error:  no legal opcode, line 16:
>> asig    osciil    10000, 110, 1
>> error:  input arg 'asig' used before defined, line 17:
>>     out    asig
>> 2 syntax errors in orchestra.  compilation invalid
>>
>> Cheers,
>> René
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I'm saying that if Csound considers the first line of the csd as line
0, where as the text editor interprets the first line as line 1, then
there would exist this offset discrepancy of 1 because the two systems
index line numbers differently. Not saying the editor itself has
anything to do with the line number generated.

Best,
Jake
-- 
The Csound Blog - http://csound.noisepages.com/

On Tue, Dec 8, 2009 at 9:40 AM, Andres Cabrera  wrote:
> Hi,
>
> It wouldn't depend on the editor as this value is generated by Csound
> alone. I've noticed some of this behavior with macros or  labels, not
> sure which. Maybe in this case it has to do with CsOptions content?
>
> Cheers,
> Andrés
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Oh.

But sometimes the error message is correct... So I think that's not
the whole picture.

Cheers,
Andrés

On Tue, Dec 8, 2009 at 6:23 PM, Jacob Joaquin  wrote:
> I'm saying that if Csound considers the first line of the csd as line
> 0, where as the text editor interprets the first line as line 1, then
> there would exist this offset discrepancy of 1 because the two systems
> index line numbers differently. Not saying the editor itself has
> anything to do with the line number generated.
>
> Best,
> Jake
> --
> The Csound Blog - http://csound.noisepages.com/
>
> On Tue, Dec 8, 2009 at 9:40 AM, Andres Cabrera  wrote:
>> Hi,
>>
>> It wouldn't depend on the editor as this value is generated by Csound
>> alone. I've noticed some of this behavior with macros or  labels, not
>> sure which. Maybe in this case it has to do with CsOptions content?
>>
>> Cheers,
>> Andrés
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"



-- 


Andrés


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

/* */ style quotes definitely don't work right when spanning multiple
lines.  Though not included in Rene's example, this is a definite bug.

Best,
Jake

On Tue, Dec 8, 2009 at 10:46 AM, Andres Cabrera  wrote:
> Oh.
>
> But sometimes the error message is correct... So I think that's not
> the whole picture.
>


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"