@ddw_music I think it is unreasonable to expect the PD help to endlessly explain how it is different from Max...
Difference from Max isn't fully the point... What I'm really driving at, perhaps clumsily, is that "use an [f], [list] or [symbol] box to cold-ify [pack]'s (well, any object's) hot inlet" is a pattern of usage that transcends object-by-object documentation. Users aren't going to get very far with Pd unless they learn a few of these key patterns and apply them generally. How do they learn them, if the help doesn't demonstrate them?
Applying them generally is another matter -- I'm asking myself the question, how is it that I taught, a month ago, how to use [f] to make a math operator cold, but I didn't think to do the same with [pack]? That's of course largely on me -- but also, if the help repeats patterns in more than one context, then the patterns enter the culture in a way that they don't if they're considered ad hoc workarounds for isolated problems. That's ultimately what I would like to see -- a handful of these object constellations becoming part of Pd lingua franca.
Fair enough to ask me to "do-ocracy" these points in the help.
@jancsika good catch on the impossibility of implementing "set." So it is a documentation matter, then.