It is now possible for a same abstraction to have message inlets/outlets in some instances, and dsp inlet/outlets in some others, while also changing all other relevant objects. Compare:
Old way:
[inlet] [inlet~] | [inlet] | [inlet~] | | | | [+ ] [+~ ] | | [inlet] [outlet~]
New way, using PureUnity (just renaming):
for floats, for signals, both
[f.inlet] [~.inlet] [$1.inlet] | [f.inlet] | [~.inlet] | [$1.inlet] | | | | | | [f.do +] [~.do +] [$1.do +] | | | [f.outlet] [~.outlet] [$1.outlet]
Evil?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
Hallo, Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
Evil?
Not in my opinion, I think it can be quite useful. I use a similar trick of $1 evaluating to an operator like + or * or to a [makefilename] argument for example in [list]-abs.
"Evil" would be this: [t b f ~]
Or not? ;)
Ciao
On Mon, 2 Jan 2006, Frank Barknecht wrote:
Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote: Not in my opinion, I think it can be quite useful. I use a similar trick of $1 evaluating to an operator like + or * or to a [makefilename] argument for example in [list]-abs.
I do this too! And I already combine both techniques, like this:
[$1.do $2]
e.g.
[commutator f +] contains [f.do +] which does [+] [commutator ~ +] contains [~.do +] which does [+~] [commutator # +] contains [#.do +] which does [# +]
"Evil" would be this: [t b f ~] Or not? ;)
Last night I made a [f.taa] and a [~.taa] so that i can order messages in abstrs that have a signal mode just by writing [$1.taa].
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada