Hi Jonathan, yeah, tables would work, I easily could keep them local any refer to the respective indices. But then again, despite what IOhannes pointed out (and I still agree with him) I like the idea of using [value]s since I could use self explaining names, which would make the mess, in this particular case, better readable.
So from this POV I don't find your solution that ugly.
Thanks, Michael.
On 25.8.2011, at 18:21 , Jonathan Wilkes wrote:
[v $0-myvalue] = associate the symbol "$0-myvalue" with a float value [expr $0-myvalue] = subtract the float value associated with the symbol "myvalue" from $0
Therefore, [expr] should always return the value of $0 (unless you're assigning a value to "myvalue" somewhere)
[expr]'s parser seems only to recognize an atom as a symbol when the first character is not a number, so try the following workarounds:
[expr _$0myvalue] [expr myvalue$0]
Both are ugly. If using tables you can avoid this mess by using an $s variable.
-Jonathan
From: Michael Zacherl. sdiy-mz01@blauwurf.info To: PD list pd-list@iem.at Sent: Thursday, August 25, 2011 11:19 AM Subject: Re: [PD] receiving messages in [expr] ?
On 25.8.2011, at 14:43 , tim vets wrote:
something like [expr myvalue] and [v myvalue]? gr, Tim
great, thanks Tim!
any chance to get $0 working? [v $0-myvalue] is fine, [bang(--[expr $0-myvalue] (might be utterly wrong) delivers strange values, not even $0.
Michael.
-- noise chasers: http://blauwurf.at http://soundcloud.com/noiseconformist
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- keep your ears open: http://blauwurf.at http://soundcloud.com/noiseconformist