especially since IIRC Max's [pack] object does use "set x" messages this way
That's a good reason to look into adding a "set" method to Pd's
looks at code for Pd's
Oh, wow-- I didn't realize that it already has an "anything" method. This means that arbitrary methods will get converted to a list which then gets resent to the object as a list.
So if you have
[hello 1 2 3(---[pack s f f f], the anything method handler converts the "hello" method to "list hello 1 2 3" and resends it so that the list gets distributed among the inlets.
Lots of great details here:
- inconsistency with
[select] and many other core objects which don't autoconvert like this
- requires allocating and freeing heap memory on every call to the anything method
- makes it impossible to ever implement the set method without breaking backward compatibility
Anyhow, if you'll tell me your desired line to add to the Purr Data docs about the lack of "set", I'll add it.
While I could also add a check and a warning for "set" messages being sent to
[pack], that risks being noisy to users who-- possibly through the use of a nested abstraction library they didn't create-- are relying on the current behavior.