thezer0ist@gmail.com

has anyone thought about making a ruby script object, along the lines of py/pyext?

and does anyone have any useful advice or example code relevant to this?

has anyone thought about making a ruby script object, along the lines of py/pyext?
and does anyone have any useful advice or example code relevant to this?


ruby

Without making any bindings to Jitter et al, it would be pretty

straightforward. Just build the ruby interpreter into an external

object and create some mechanism for loading scripts and talking to

inlets and outlets. Check out the Ruby C interface for more details

http://www.ruby-lang.org/en/documentation/

http://www.ruby-doc.org/doxygen/current/group__ruby__ruby.html

http://www.ruby-doc.org/doxygen/current/group__ruby__interp.html

> has anyone thought about making a ruby script object, along the lines of py/pyext?

> and does anyone have any useful advice or example code relevant to this?

Without making any bindings to Jitter et al, it would be pretty
straightforward.  Just build the ruby interpreter into an external
object and create some mechanism for loading scripts and talking to
inlets and outlets.  Check out the Ruby C interface for more details
on how to do this:

Particularly the Ruby module:
http://www.ruby-doc.org/doxygen/current/group__ruby__ruby.html

And the Interpreter Interface:
http://www.ruby-doc.org/doxygen/current/group__ruby__interp.html

On 3/19/07, thezer0ist  wrote:
>
> has anyone thought about making a ruby script object, along the lines of py/pyext?
> and does anyone have any useful advice or example code relevant to this?
>


On 19 Mar 2007, at 23:15, Wesley Smith wrote:

> Just build the ruby interpreter into an external

> object and create some mechanism for loading scripts and talking to

> Just build the ruby interpreter into an external
> object and create some mechanism for loading scripts and talking to
> inlets and outlets.

i've considered doing that, but it feels like that might be one too many levels of indirection. it'd be nice to not have to bridge it through another language. then again, perhaps that doesn't really matter.

i've considered doing that, but it feels like that might be one too many levels of indirection. it'd be nice to not have to bridge it through another language. then again, perhaps that doesn't really matter.
thanks for the suggestion.


ruby?