This still is not supported in IronRuby, as the version of the CLR on the Windows Phone (at least last i checked) was really the compact framework, which does not support any types usually found in the full .NET Framework's System.Reflection.Emit namespace. Therefore, IronRuby cannot emit the correct backing class. The ref params is also a CF limitation.
We were thinking of doing some static analysis to generate C# code which when compiled would produce the required static types, and then know to use those as backing types, but any static analysis solution would not always work in a dynamic language. I haven't used WP7 devtools in a while, so I'd be curious if the Ref.Emit limitation still exists in Mango, but I suspect it is still an issue. ~Jimmy On Dec 11, 2011, at 12:29 PM, "Andrei N." <li...@ruby-forum.com> wrote: > Hi, > > In the article from 2010, Tomáš was describing the limitations on WP7: > http://matousek.wordpress.com/2010/03/21/ironruby-on-your-phone/ > > "The most significant are calls to methods with out or ref parameters. > You also won’t be able to inherit a Ruby class from a CLR class or > implement a CLR interface since that requires us to emit a proper CLR > type. We are going to address both of these limitations in future > versions." > > > Are these two addressed in the latest version of IronRuby for WP7? > > Thanks! > > -- > 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
