Re: Problems with Ruby in C

On Tue, Feb 19, 2002 at 01:21:31PM +0900, Yukihiro Matsumoto wrote:

Thanks for the answers matz, they helped me understand this a bit
better. Though they, of course, resulted in my questions :)

> the assignemnt to the variable a is done in the scope of the execute
> method, whic vaporized every time execute called.  On the other hand,
> 
> |static VALUE cContext_execute(VALUE self, VALUE str)
> |{
> |    return rb_funcall(self, rb_intern("instance_eval"), 1, str);
> |}
> 
> this case, the assignment is done at the toplevel scope, which is used
> again and again.  That's the difference.

Ah, I understand now. So is there an easy and nice way to make something
execute inside a scope from C? What I did now was to rip out PUSH_SCOPE
and POP_SCOPE from eval.c and put them around the eval like this:

    PUSH_SCOPE();
    v = rb_funcall(self, rb_intern("eval"), 1, str);
    POP_SCOPE();

so I now get

"
5
undefined local variable or method `a' for #<Context:0x401b5af4>
"

when I run the program, which is what I want. But it feels a bit like
language abuse to do it the way I'm doing it now.

(I've attached the whole program to this mail if someone wants to see it.)


The next problem I'm having is that I want to be able to return from the
the eval. I.e. I want to be able to evaluate something like this:

    a = 1
    if a == 1
        return "a is one"
    else
        return "a is not one"
    end

which means it has to be evaluated inside a method somehow. That's why I
put the eval/instance_eval call inside the execute method, which I
define in the Context class, because I thought that it might then be
evaluated inside that method.
But it's not working. If I remove rb_protect which is protecting the
call to cContext_execute_helper I get segmentation faults. So I'm
obviously doing something wrong, the question is what?

Is this even possible?


/joakim

-- 
Joakim Andersson ; [e-mail] ; http://borgship.net/~tyrak/