[PD] nested nqpoly4's

Jonathan Wilkes jancsika at yahoo.com
Sat Feb 18 16:53:37 CET 2012

Pd somehow checks for abstractions nested inside themselves and refuses to create the inner one(s).
Obviously under normal circumstances such self-nested abstractions would expand to infinity.
Can Pd tell the difference between dynamically instantiated objects and "normal" instantiation?
If not, you'll be forced to solve the halting problem to be able to get what you want, or else put an arbitrary 
limit on abstraction nesting depth (like Pd's recursion).

>From: James Mckernon <jmckernon at gmail.com>
>To: pd-list at iem.at 
>Sent: Saturday, February 18, 2012 9:47 AM
>Subject: [PD] nested nqpoly4's
>Hi all,
>I've noticed that nesting nqpoly4 doesn't seem to work. i.e., if a patch contains an nqpoly4 of patchX, and patchX contains an nqpoly4 of patchY, then the patchY's will not instantiate. Instead, a bunch of 'connection failed' messages appear in pd's console.
>Is this a known bug? Any workarounds? I did discover that opening and saving patchY will cause its nqpoly4 to reload, and then instantiate properly, but I don't feel this is a good solution for regular use.
>Pd-list at iem.at mailing list
>UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

More information about the Pd-list mailing list