[PD] pd message order?

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-08-04 00:06, Jonathan Wilkes wrote:
> Technically it seems to be this: they output in reverse creation order. (The last [receive] you created in the patch will output first.)
> 
> 
> Conceptually, imagine an evil demon changing the order in real-time to screw up your patch.  Thwart the demon by using wired connections, trigger, and subpatches to define order.  Only use multiple [receive]s when message order doesn't matter. (Same with multiple wires fanning out to various objects from an outlet.)
> 

exactement.
that's what i teach my students: don't ever use [receive] if you _might_
depend on execution order.

and then there is iemgut's [oreceive] (which stands for Ordered
RECEIVE), where you can specify a priority, so you have control over
execution order (it's also in Gem known as [gemreceive])

fgamsdrI
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk46S8MACgkQkX2Xpv6ydvT9awCgjDVu45SzeOe4LmCLuxH/0wZ/
tPwAnRqSqA9xg0XtBBgZyFZOeq3lFpN0
=l9+8
-----END PGP SIGNATURE-----

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3636 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20110804/3b183827/attachment-0001.bin>