On Thu, Mar 12, 2009 at 6:21 PM, Luke Iannini lukexipd@gmail.com wrote:
Yes, the better solution methinks would be a vanilla* "savebang" to clear out the dynamic subpatch just before save. But I suppose that requires acknowledging dynamic patching.
lxi
*the [tot]-based method just does not work reliably
To mention programming languages, here (I wouldn't propose to open this can of worms, but to look at the options for a more complete programming style in Pd)
I think this makes sense from a programming languages point of view. If you're creating a dynamic-based abstraction, it should be analogous to writing a class.
There is a way to write the code for a "new" or "create" routine in your class via [loadbang], so you need a way to code a "free" or "delete" routine as well.
A selective-save feature would be a more pragmatic approach for Pd users. I think of data-structures in C, where you add a pointer in your struct. You can later dynamically allocate memory for an array and set the pointer, but the structure itself does not include the dynamically created array. However, I think that coding a new method would be expensive and problematic.
What set of operations is necessary to be able to create dynamic patching capability? Do you think there's a top-down design based approach to outline the necessary principles for it?
Chuck