[Ironruby-core] interop question

Curt Hagenlocher curth at microsoft.com
Tue May 12 16:35:10 EDT 2009

But this redirection can be done entirely at the level of Ruby metaprogramming, can’t it. I’m pretty sure I’ve seen Proxy objects defined in ActiveSupport that do something quite similar. (Full disclosure, though: I’m really a Ruby noob.)

By contrast, consider the following

class C
  clr_property :Value, System::Int32, ::get_value, ::set_value

  def get_value
  def set_value
    raise RuntimeError, 'Read-only, sucker!'

The hypothetical class method clr_property might set some kind of metadata on the class which would be picked up by the CLS type generator, and turned into a CLS-visible property on the generated type with getter and setter methods. This is the sort of thing I had in mind when I described “additional metadata”.

From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Ivan Porto Carrero
Sent: Tuesday, May 12, 2009 12:58 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] interop question

About the metadata.. I think in my case it would be great if I could redirect the methods on the type to methods on a property of that type.

So for the ShurikenProxy class I would like to say that it needs to forward all method calls to the property subject for example possibly with an exception list of methods that won't be forwarded. I guess that would get me the behavior I'm expecting. Would that be possible?
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

On Tue, May 12, 2009 at 4:49 PM, Curt Hagenlocher <curth at microsoft.com<mailto:curth at microsoft.com>> wrote:

We can’t apply all Ruby standards when we travel back to staticland.

When you define and use a Ruby class, we need to create a static CLR type to represent that class. This underlying type is constrained by what can be done with CLR types; and in particular, it’s structure is immutable. So we can’t just go back to this type and tell it that it should now implement IWeapon – we need to have known this at the time the class is created.

Now, it’s possible to be pretty flexible about the ingredients that go into the type. So if the IronRuby community decides to change how this underlying type is created – perhaps by taking additional metadata into account – then that’s no problem. But as soon as you create the first instance of ShurikenProxy, that’s when we need to freeze things and actually emit the type.

In this particular case, when creating a proxy for an object that implements certain CLR interfaces, the proxy itself will have to implement the same interfaces if the object is going to be passed back to static code. But Ruby’s metaprogramming makes this pretty easy – get all ancestors of class Module whose to_clr_type is not nil, and simply include those into a newly-created proxy class programmatically.

From: ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org> [mailto:ironruby-core-bounces at rubyforge.org<mailto:ironruby-core-bounces at rubyforge.org>] On Behalf Of Ivan Porto Carrero
Sent: Tuesday, May 12, 2009 12:23 AM
To: ironruby-core
Subject: [Ironruby-core] interop question

Let's say I have these interfaces

public interface IWeapon{

        void Attack(IWarrior warrior);

        int Damage();


    public interface IWarrior


        int Id { get; }

        string Name { get; set; }

        bool IsKilledBy(IWeapon weapon);

        void Attack(IWarrior target, IWeapon weapon);


And one implementor defined in C#

public class Ninja : IWarrior{

        private readonly int _id;

        public string Name { get; set; }

        public int Id { get { return _id; } }

        public void Attack(IWarrior target, IWeapon weapon){



        public bool IsKilledBy(IWeapon weapon)


            return weapon.Damage() > 3;



Now if I create an implementation of IWeapon in Ruby

class Shuriken

   include IWeapon

   def damage




which I then proceed to wrap in a forwarding class

class ShurikenProxy

  instance_methods.each do |name|

      undef_method name unless name =~ /^__|^instance_eval$/


   def initialize

      @subject = Shuriken.new


  def method_missing(m, *a, &b)

     @subject.send(m, *a, &b)



Then I would expect this to work:

ninja = Ninja.new

ninja.is_killed_by ShurikenProxy.new

only it tells me that the ruby object isn't an implementation of IWeapon

while by all ruby standards it is. if you ask it for its ancestors it's got IWeapon there

if you ask it for its class it tells you Shuriken and not ShurikenProxy

Is that supposed to happen?

Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero
Blog: http://flanders.co.nz
Twitter: http://twitter.com/casualjim
Author of IronRuby in Action (http://manning.com/carrero)

Emma Goldman<http://www.brainyquote.com/quotes/authors/e/emma_goldman.html>  - "If voting changed anything, they'd make it illegal."

Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090512/5753f99b/attachment.html>

More information about the Ironruby-core mailing list