hi list
using $0-prepended local variables and $1-prepended arguments in message boxes is really a pain. would it make any sense to allow some type of escape character to make it easier?
for example, a $$1 would refer to an argument to the subwindow, but a $1 would still refer to a variable passed to the message box? or some similar code...
hope this makes sense, it's early morning here :)
eric
Eric,
At first glance this looks like a bad thing.
But when I think about all the trouble I go through to get $ arguments into messages I think this would solve that nicely...
David
. . David McCallum . Music wants to be free . http://mentalfloss.ca/sintheta .
Eric Skogen wrote:
hi list
using $0-prepended local variables and $1-prepended arguments in message boxes is really a pain. would it make any sense to allow some type of escape character to make it easier?
for example, a $$1 would refer to an argument to the subwindow, but a $1 would still refer to a variable passed to the message box? or some similar code...
hope this makes sense, it's early morning here :)
eric
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
At first glance this looks like a bad thing.
But when I think about all the trouble I go through to get $ arguments into messages I think this would solve that nicely...
While we're at it: I would *LOVE* to have a variable length argument called $* as in bash, that just matches all incoming messages. Then someting like prepend would become unnecessary and we could send variable length lists.
Another thing would be a settable [route], where [route] would act like [select] without arguments. There is an xroute with source at http://www.cycling74.com/share/jhno/ but I cannot unpack the archive.
Ah, X-mas time...
ciao
Frank Barknecht _ ______footils.org__
Frank Barknecht wrote:
Hallo, David NG McCallum hat gesagt: // David NG McCallum wrote:
At first glance this looks like a bad thing.
But when I think about all the trouble I go through to get $ arguments into messages I think this would solve that nicely...
While we're at it: I would *LOVE* to have a variable length argument called $* as in bash, that just matches all incoming messages. Then
isn't this $@ ?
and while we are at it: $# would be cool too.
and yes indeed, i would *love* this too
mfg.asd.r IOhannes
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
Frank Barknecht wrote:
While we're at it: I would *LOVE* to have a variable length argument called $* as in bash, that just matches all incoming messages. Then
isn't this $@ ?
$* and $@ are almost the same, only quoting is handled differnently. See section "Special Parameters" in bash(1)
and while we are at it: $# would be cool too.
You got me. ;)
ciao
Frank Barknecht _ ______footils.org__
And if this aspect of PD changes, please please, add a complete character escape mechanism, to be able to get literal '$', newline, backslash, comma, semicolomn, and spaces in a symbol.
Now pd is only 99% compatible with ASCII. I think the escape mechanism can be compatible with old patches, since there are only numbers used after a '$'.
That would allow to send eg. "set $; target1 $$*" to a message box.
regards, j#|@
Frank Barknecht wrote:
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
Frank Barknecht wrote:
While we're at it: I would *LOVE* to have a variable length argument called $* as in bash, that just matches all incoming messages. Then
isn't this $@ ?
$* and $@ are almost the same, only quoting is handled differnently. See section "Special Parameters" in bash(1)
and while we are at it: $# would be cool too.
You got me. ;)
ciao
-
David NG McCallum -
Eric Skogen -
Frank Barknecht -
IOhannes m zmoelnig -
Johannes Taelman