Hi Matt,

yap, I got your point guys, and as I said I never rely on this kind of things (that's why [trigger] extists ;) ), so we're on the same page here. but I would disagree with the "there is no point in trying to understand how it works" part. I think it's important to be aware of the tool. for example, the way I came across this is while I was debugging a big patch. I think that knowing about this "order of operation" thing would have helped me understanding what's going on (because there's a rule behind it, that of course like you said could change in the future - risky thing changing this kind of things in my view - but it's matter of fact now is there) . at the end of the day I found the issue in my patch, but almost certainly would have taken me less time if I knew this.

cheers, Mario

On 10 July 2018 at 21:05, Matt Davey hard.off@gmail.com wrote:

iohannes’ point was that even if there is a ‘rule’, you should not depend on it, and it may change in the future, so basically there is no rule. Don’t depend on that always working.

There is no point in trying to understand how it works. Just assume it’s random.

On Tuesday, July 10, 2018, mario buoninfante mario.buoninfante@gmail.com wrote:

...

Hi I0hannes,

thanks for your reply. you're definitely right, in fact that's how I wrote my patch, I probably kept my question to vague. it's not a problem, I can see several workarounds for that, so it's fine, it's more about better understanding what's going on under the hood. I always use [t] to be sure that the oder of operation is correct, but I also know that there's a "rule" about the order of connection. so my question would be, is there any rule behind the [send] and [return] behavior?

cheers,

Mario

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/li stinfo/pd-list