Try implementing TryInvokeMember. In IronRuby "d.foo" actually gets and invokes "foo", so it will use DynamicObject's TryInvokeMember. This is different from IronPython and C# where method calls are two operations: TryGetMember (d.Foo) and TryInvoke (d.Foo()). The rough IronRuby equivalent to this is d.method(:foo).call().
~js On Sep 9, 2011, at 2:45 AM, Benjamin Joldersma wrote: > I am working with IronRuby and a DynamicObject derived class to create a > proxy layer for a game scripting engine that allows me to intercept gets > and sets and do things like mark objects for saving, potentially > security checks, etc. > > But I'm finding that if my TryGetMember returns true, but sets the out > result param to null, then IronRuby seems to hang indefinitely. > > I've created a pretty concise repro case here: > > https://gist.github.com/1205629 > > can anyone shed some insight into this problem? So far, I'm loving > IronRuby. > > best, > > --ben joldersma > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core