No, the instr lines below don't work without the backslash either. (Still 
generates a "no legal opcode" message - at least in Windows XP.)

The backslash character is supposed to be the character that permits 
continuation lines in an orc.

This is not a big problem - but is it a bug?

Art Hunkins

----- Original Message ----- 
From: "Art Hunkins" 
To: 
Sent: Tuesday, March 11, 2008 9:53 PM
Subject: Orc Syntax Query


> Today I noticed that the following statement generates a "no legal opcode" 
> error (on line 2):

 instr 1, 2, 3, 4, 5, 6, 7, 8, \
 9, 10, 11, 12, 13, 14, 15, 16

> Should it?
>
> (I've got a line of 32 instrument numbers I'd like to break up for 
> readability.)
>
> Art Hunkins 

> 
>> Today I noticed that the following statement generates a "no legal 
>> opcode" error (on line 2):
> 
> instr 1, 2, 3, 4, 5, 6, 7, 8, \ 
> 9, 10, 11, 12, 13, 14, 15, 16
> 

There appears to be a space after the backslash,
which would mean that the space is being escaped
rather than the newline.

Tobiah

I just tried this with the intel OS X 5.08 beta.  It works fine for me, with
and without trailing whitespace.  Perhaps this is a 5.07 issue?

Since we're on the topic of potential syntax bugs.  The following does not
work in both the orc and score if $test hasn't been defined:

/*
$test
*/


Best, 
Jake 
---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog/






Tobiah-3 wrote:
> 
>>> Today I noticed that the following statement generates a "no legal 
>>> opcode" error (on line 2):
>> 
>> instr 1, 2, 3, 4, 5, 6, 7, 8, \ 
>> 9, 10, 11, 12, 13, 14, 15, 16
>> 
> 
> There appears to be a space after the backslash,
> which would mean that the space is being escaped
> rather than the newline.
> 

-- 
View this message in context: http://www.nabble.com/Fw%3A-Orc-Syntax-Query-tp16039849p16060465.html
Sent from the Csound - General mailing list archive at Nabble.com.