[Ironruby-core] Working on Seo's r144 patch
curth at microsoft.com
Fri Sep 19 07:47:20 EDT 2008
We haven't yet written the transformation script for IronRuby to move namespaces from System to Microsoft. It should happen soon.
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Stefan Dobrev
Sent: Friday, September 19, 2008 1:07 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Working on Seo's r144 patch
Check out this blog post:
2008/9/17 Seo Sanghyeon <sanxiyn at gmail.com<mailto:sanxiyn at gmail.com>>
2008/9/18 C.J. Adams-Collier <cjac at colliertech.org<mailto:cjac at colliertech.org>>:
> Seo mentioned to the IRC channel the other day that he got r144
> building, so I thought I'd try it. I didn't get it working, so I'll
> post my results here.
Your log indicates that it builds fine up to IronRuby.dll. Now when you build
IronRuby.Libraries.dll, System.Core.dll is referenced again. I believe
the story goes
something like this:
Mono gmcs references System.Core.dll by default.
Mono gmcs /noconfig avoids referencing System.Core.dll.
However, ExtensionAttribute is in System.Core.dll, and due to current limitation
of Mono gmcs, it needs to reference System.Core.dll in order to compile
extension methods correctly.
DLR does not use extension methods.
IronRuby.dll uses extension methods, but none of assemblies IronRuby.dll
references use extension methods.
IronRuby.Libraries.dll uses extension methods, and references IronRuby.dll
which uses extension methods. System.Core.dll is pulled in, classes are defined
multiple times, FAIL.
Ironruby-core mailing list
Ironruby-core at rubyforge.org<mailto:Ironruby-core at rubyforge.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironruby-core