----- Original Message -----
From: IOhannes m zmoelnig zmoelnig@iem.at To: pd-list@iem.at Cc: Sent: Monday, May 14, 2012 3:42 AM Subject: Re: [PD] variable receive objects?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-05-14 05:02, John Harrison wrote:
I thought [send13] and [receive13] from the ext13 library were for settable send and receive? Or am I misunderstanding the question?
for settable send i would _highly_ recommend to use the built-in [send]. whether you use [iem_r] or [receive13] is probably only a matter of taste (but i think that most of ext13's objects are not so important nowadays; and d13b is not so active in Pd land any more)
I've used those 2 objects a lot and thought they seemed pretty stable...
that's because the "trivial" case (where receiving data and changing the receive label are completely independent of each other (stackwise)) won't create much of a problem.
Well, with [iem_r foo] I tried recursion while changing the rcv-symbol at various points, sending multiple messages with a [; foo set bar] nested in the middle, and making two [iem_r] objects and having the first one that receives a message trigger a [set bar( to the 2nd one _before_ the 2nd one receives its message. None of these trigger a crash.
How do I manifest the bug?
-Jonathan
it's easy to implement a feature and suddenly end up with a bug. it's even common. both [recevie13] and [iem_receive] have probably gone this route. however, it's incredibly harder to implement a feature where you know beforehand that you will open a can of worms and you don't know yet how to close it (properly). that's the route [r] has gone.
fgmasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+wt1AACgkQkX2Xpv6ydvT2LACg5wh3vPHkGrtpNDHGs71QJHb6 84IAoNn0OViWhBvmjEof24UTJPWmcfnp =pvRn -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list