BasicObject's instance methods

[catsidhe]

BasicObject.instance_methods

Ruby:

[:!, :==, :!=, :__send__, :equal?, :instance_eval, :instance_exec, :__id__]

mruby:

[:method_missing, :initialize, :!]

Is there a reason for this difference? In particular, #__send__ can be pretty useful.

One workaround is to use eval("obj.#{method_name}(*args, &block)"), but it's obviously a poor solution.

Another potential workaround:

Kernel.instance_method(:send).bind(obj).call(:method_name)

crashes with:

Segmentation fault: 11

(both Object and BasicObject)

[ksss]

It's interesting.
I don't know why BasicObject#__send__ is nothing.

But,

Kernel.instance_method(:send).bind(obj).call(:method_name)

It might be mruby-method's problem.
I'll check it later.

[matz]

I made BasicObject compatible with CRuby, with two exceptions:

• binding is not implemented for mruby
• instance_exec which is implemented in mruby-object-ext gem and moving it to BasicObject is difficult. I don't think it's worth the price of implementation complexity.
  The SEGV issue is very interesting, but since it is a separate issue (probably) in mruby-method, it should be treated independently.

[ksss]

ksss/mruby-method side solved at 8a15abd
Thanks