sending same message to different [receive] objects
…one by one – a [forward] task?
cheers!
-jonas
pattrforward may be a better approach – no receive objects, clearly defined hierarchical namespace.
Or use a single receive object name combined with route.
thanks for the replies! but I guess both approaches won’t do – at least not fully (for the [route] method simply loses in its looks, hehe).
I guess I’ll stick to my [sprintf] [forward] combination. thank you anyways!
all the best
-j
To be clear, I meant putting one route object in each subpatch. I often use a code style like that to simulate a "namespace hierarchy".
I usually avoid the pattr objects as I believe they have some fundamental design mistakes.
For example:
I might add that generating symbol names through sprint is necessary in other circumstances, for instance generating unique names for colls and buffers inside abstractions.
I still believe that you should minimize the number of global symbols you use though, especially for receive objects.