Terry Cast wrote:
> 
> Well, one reason (maybe or maybe not the only reason, and maybe or maybe not a
> sufficient reason) is that those of us who don't know C would have to learn a whole
> new syntax.

Unless it could be done without breaking old syntax... that is,
aout opcode arg1, arg2, arg3

would be interpreted the same as

aout = opcode(arg1, arg2, arg3)


Personally I think that would be pretty darn cool!

But I'm guessing it might be a non-trivial project? It would be
important to preserve existing behavior ...

The if/elsif/else blocks, on the other hand, would be a VERY nice
feature, and I can't see how it could hurt anything. It also strikes me
as more important than adding punctuation in the style of C or any other
popular language, as nice as that could be.  I find reading other
people's csound orcs to be very difficult if they're at all complex, and
nicer block structures would help.

You could also take it code blocking one step further and add orc based
functions
as well....(I know this is a silly example...)

For example:

arate	My_Oscillator(iPitch){

	a1 = oscili iPitch,3000,1
	return a1
}


instr 1
	aout = My_Oscillator(440)
endin


Maybe this to.....?

	aout = balance(My_Oscillator(440),a2,a3)


Dustin Barlow
dbarlow@omnids.com