On 05/14/2013 02:49 PM, Miller Puckette wrote:
Interesting idea. I agree that a non-lazy dev could just make argument strings serve the same function (and sometimes it's good to see all the args up front to prevent unnecessary allocations or computation).
Here's a thing to think about - how could abstractions (as opposed to externs) catch and use mesages separated by commas? There are lots of things abstractions can't do cleanly (like have variable numbers of inlets/outlets) and perhaps it could be helpful to use after-creation messages somehow for this. (I've always been nervous about the widespread use of self-modifying patches to fill this need :)
cheers Miller
This may be a totally stupid idea but here it goes anyhow... What about creating a special nlet object that can dynamically change the number of nlets (in or out depending on a flag given) and issue command to gop object to redraw itself upon update? Doesn't seem to hard to implement but it does seem a bit unconventional, if you like...