hi all,
is it possible to use a variable such as $0-bla in an expr object? using it this way, expr doesn't recorgnize this as a variable ...
thnx...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Try putting spaces on either side of the "$0-blah" symbol - that way Pd thinks it's a separate argument and should expand it.
cheers Miller
On Wed, Feb 18, 2004 at 02:46:20PM +0100, Tim Blechmann wrote:
hi all,
is it possible to use a variable such as $0-bla in an expr object? using it this way, expr doesn't recorgnize this as a variable ...
thnx...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
hi miller,
On Wed, 18 Feb 2004 09:24:40 -0800 Miller Puckette mpuckett@man104-1.ucsd.edu wrote:
Try putting spaces on either side of the "$0-blah" symbol - that way Pd thinks it's a separate argument and should expand it.
i tried this without succes: if i bang _expr $0-bla_ i get the value of $0 as return value and _error: no such var 'bla'_ and i'm not able to create objects like $0bla or $0_bla ...
any idea?
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Miller, Tim, list,
Being confronted to this issue right now i would like to know if this old discussion has ever been solved ?
+! aym3ric.
hi miller,
On Wed, 18 Feb 2004 09:24:40 -0800 Miller Puckette mpuckett@man104-1.ucsd.edu wrote:
Try putting spaces on either side of the "$0-blah" symbol - that way Pd thinks it's a separate argument and should expand it.
i tried this without succes: if i bang _expr $0-bla_ i get the value of $0 as return value and _error: no such var 'bla'_ and i'm not able to create objects like $0bla or $0_bla ...
any idea?
cheers...
Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
Being confronted to this issue right now i would like to know if this old discussion has ever been solved ?
i don't think that the behaviour changed ...
i switched to k_cext for the specific tasks ... there you can access a $x value with the macro VALUE(" $x-bla") (the space in frond of the $ is necessary to replace the $x with the argument ....
cheers... tim
hello,
Being confronted to this issue right now i would like to know if this old discussion has ever been solved ?
i don't think that the behaviour changed ...
i switched to k_cext for the specific tasks ... there you can access a $x value with the macro VALUE(" $x-bla") (the space in frond of the $ is necessary to replace the $x with the argument ....
thx for the info tim. unfortunately i wanted to avoid any externals for this patch (i mean any extra externals not present in the pd bundle). i guess i'm going to have to remplace my expr with simple operators ... jeez ... i'm going to love this .. :)
i think this $0 support would be a nice thing to add in the expr todo list :)
+! aym3ric.
With the latest versions of flext, dyn~ and py/pyext with Pd from cvs on Linux, It is now possible to dynamically create and connect (from a Python script via ethernet for e.g. :-) complex Pd objects which may contains py/pyext objects... This sounds to me like a beautiful step toward the integration of a simply powerfull OO scripting-language and a real-time system. many thanks to Thomas Grill (among many others of course) for making it possible.
some details:
modifications for this combination to work. afaik the latest pd release still produces "stack overflow" errors when using py/pyext and crashes when trying to use dyn for the creation of py/pyext objects. Might be useful for windows users who do not necessarily want to handle all the compilation work for example.
very much slowed down (while pd -alsa is working like a charm).
sincere greetings to the puredata community, vincent
Hi Vincent, many thanks for your mail.
Some notes:
With the latest versions of flext, dyn~ and py/pyext with Pd from cvs on
Linux,
It is now possible to dynamically create and connect (from a Python script via ethernet for e.g. :-) complex Pd objects which may contains py/pyext objects... This sounds to me like a beautiful step toward the integration of a simply powerfull OO scripting-language and a real-time system.
I'm working on an even tighter integration where PD objects can be directly managed by object-oriented C or Python code, without the detour of message generation. This can then be used for dynamic patching or just another patcher system.
- It would be nice if the official Pd release could integrate the needed
modifications for this combination to work. afaik the latest pd release still produces "stack overflow" errors when using py/pyext and crashes
when
trying to use dyn for the creation of py/pyext objects. Might be useful
for
windows users who do not necessarily want to handle all the compilation work for example.
I'm not aware that the stack overflow happens under Windows as well - i thought it's only when using linux. Could you send me a simple patch with the crashing py/pyext-dyn combination?
- I noticed that when using "pd -jack" the ouput of py/pyext objects is
very much slowed down (while pd -alsa is working like a charm).
I'll have to investigate but it may take a while since i'm not running jack at the moment.
best greetings, Thomas
unfortunately i wanted to avoid any externals for this patch (i mean any extra externals not present in the pd bundle). i guess i'm going to have to remplace my expr with simple operators ... jeez ... i'm going to love this .. :)
i think this $0 support would be a nice thing to add in the expr todo list :)
the problem is a more general one ... if you have a symbol $0-bla, expr has no knowledge, if it's a symbol "$0-bla" or the term "$0 - bla" ...
probably there will have to be some macro to access values ...
cheers... tim
hi thomas,
I'm working on an even tighter integration where PD objects can be directly managed by object-oriented C or Python code, without the detour of message generation. This can then be used for dynamic patching or just another patcher system.
very interesting.
can you elaborate on this a bit more? i'm trying to do something similar with mole and pf, but i'm stuck at the point where i need to catch the objects's output and map it to a function return value..
tom
Hi Tom,
I'm working on an even tighter integration where PD objects can be directly managed by object-oriented C or Python code, without the detour of message generation. This can then be used for dynamic patching or just another patcher system.
very interesting.
can you elaborate on this a bit more?
the project is still in the concept stage, but it will be a topic for the PD convention in Graz. In short words, it will be a shared library with a C-style API that acts as an interface to the PD system. It's built on top of the traditional API and i don't think that changes to PD are needed. It will manage construction, destruction, connection of objects and storage of associated additional data. Just as with dyn~ the objects will live in a sandbox, they will not appear in the tcl/tk patcher system.
i'm trying to do something similar with mole and pf, but i'm stuck at the point where i need to catch the objects's output and map it to a function return value..
In dyn~ this is done with "proxy" objects that are connected to the objects of interest.
best greetings, Thomas