this bus discussion makes want to bring up something --

am i wrong in thinking that csound5 is an opportunity to 'slash and burn'
a lot of code and csound language into something less redundant, more
simple, and hopefully more elegant?

i already alluded to reducing all a-rate and k-rate i/o into just one
'out' and one 'in' opcode.  i also think this would be a great time to get
string parameters implemented wherever possible - i should have
been making a list, but 'named' functions and then 'named' bus channels
come to mind ..


-m