I'd be fine with dropping support for *Desktop* v2.0. We need to support Silverlight 3 builds though so that we continue running on Windows Phone 7. This essentially means we can't get rid of the inner ring just yet. Do you consider supporting IronPython on Windows Phone too? The only work that's needed there is to interpret call-sites instead of compiling them. Some of them already do so but there are others that don't. Plus you'd need a bit refactoring to avoid referring Ref.Emit types in common code paths.
Overall I don't think dropping v2.0 build buys us that much if we need Silverlight 3 build anyways. Do you experience problems or excessive amount of work supporting v2.0 builds? Tomas -----Original Message----- From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Jeff Hardy Sent: Wednesday, April 06, 2011 2:27 PM To: ironruby-core@rubyforge.org Subject: [Ironruby-core] Dropping .NET 2.0 Support for IronRuby Right now, the plan is for IronPython to drop support for .NET 2.0 and be .NET 4 only for the 3.0 release (which is probably still a year or more away). Are there any similar plans for IronRuby? IP can drop 2.0 support without impacting IR at all (I think), but if there plans to drop it from IR as well we can trim up the repository somewhat (in particular, the DLR inner ring could be removed and live in the Mono tree, or something like that). - Jeff _______________________________________________ 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
