... at the usual place:
http://www.zogotounga.net/comp/csoundx.html

includes a few fixes, and updated syntax-highlighting for 5.12 (notably 
the new signal flow graph opcodes)

as always, feedback is welcome


Stef




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> You might find the file opcodes.xml from the manual sources useful for
> syntax highlighthing (It contains all the opcodes in the manual with
> their description), since it's kept up to date with the manual:

hi,

yes I'm aware of this. csound-x has its own way to parse the manual 
though, and a specific classification for opcodes which make them be 
highlighted differently according to what they do and how they are used.

best,

Stef




Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

> Could you elaborate on this a bit?

Sure. I base my classification on several points, among which: the 
number of output arguments, weither we are talking about an opcode or a 
function, the chapter of the opcode in the manual, "special opcodes", 
"I/O opcodes", "control flow opcodes", where the three last sets are 
more or less hard-coded.

For example, although "outleta" is an opcode classified in the manual 
under "signal flow graph", I prefer to have it displayed as an I/O 
opcode: it stands out in the same way as "outs" within an instrument 
definition. See the attached example for illustration (it's how Mike 
Gogin's piece in the latest Csound Journal shows by default)

cheers,

Stef

Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks, I was curious as to how you classified things.

Cheers,
Andrés

2010/5/25 Stéphane Rollandin :
>> Could you elaborate on this a bit?
>
> Sure. I base my classification on several points, among which: the number of
> output arguments, weither we are talking about an opcode or a function, the
> chapter of the opcode in the manual, "special opcodes", "I/O opcodes",
> "control flow opcodes", where the three last sets are more or less
> hard-coded.
>
> For example, although "outleta" is an opcode classified in the manual under
> "signal flow graph", I prefer to have it displayed as an I/O opcode: it
> stands out in the same way as "outs" within an instrument definition. See
> the attached example for illustration (it's how Mike Gogin's piece in the
> latest Csound Journal shows by default)
>
> cheers,
>
> Stef
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"