Is there any disadvantages to using the send and receive objects compared to direct connections? - does it use any more cpu?

What happens when there is more than one receive for a send? - what order are these executed in? I know for direct connection its good practice to use the trigger object to give predictable sequencing. Presumably then if using send to multiple receives you really need to use the trigger object and give a new unique name to each send / receive?

I attach an example to show what I mean

srtestjjl.pd

@JJLloyd Yes, like other connections, the order will depend on the order in which they were created, so triggers are always best, and you can guarantee delivery order by using different names if it is important.
As Pd builds the patch from your "visual" there will be no difference between [outlet] >> [inlet] and [send] >> [receive]....... the same number of "jumps".
A direct connection is probably faster, but with processors running as fast as they do nowadays......by anything noticeable?
[s] and [r] certainly keep a patch tidy and human readable, and are worth any cpu I think. The cpu is not doing much work there, just writing and reading ram.
David.

@whale-av Thanks David. I guess the same also applies to the hidden send and receives within GUI objects. These seem neat, although, I think maybe may risk being obscure when code is reviewed at some time after being written.

Jim

@JJLloyd Yes, but it is still possible to use [s]/[r] and the hidden sends/receives in the GUI objects without losing control over the order of operations.

For example, here both number boxes on the left (main GUI) send to the number boxes on the right and the values are stored in [f] objects using the cold inlets.

When the code executes by using the bang, the order of operations is completely defined:

@ingox Many thanks - really useful tip. I think getting clear in the mind about order and hot/cold inlets is critical for new beginners with Pd

Jim