It's not the list management that's the problem, it's having a way to track down all stale pointers and un-point them. Currently this is managed by maintaining a per-list "stub" that the pointers all check through. one could have such a stub for every scalar, but this would add a lot of overhead. Alternatively, all "gpointers" to a given scalar could register themselves somehow, and every time one deleted a scalar one would track down every pointer to it through the registration mechanism. I've been unable to convince myself that the machinery could be kept lightweight and efficient.
cheers Miller
On Tue, Jul 08, 2008 at 03:04:29AM -0400, Mathieu Bouchard wrote:
On Sat, 14 Jun 2008, Miller Puckette wrote:
I'm thinking about making a message to "pointer" that deletes the object after the pointed-to one (thus leaving the pointer itself unchanged) -- the gotch is that it would "stalify" all other pointers to the list, at least as things are currently implemented.
So, why are singly-linked-lists so crucial to the design of Pd ?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - t?l:+1.514.383.3801, Montr?al, Qu?bec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list