Re: [Ironruby-core] Rake error with IronRuby on Mono - PathName2 / System.dll

2010-03-08 Thread Cory Foy
Hi Ivan, Ivan Porto Carrero wrote: It's a pitty those instructions are around because they are really outdated you can get a mono built binary for RC2 here: http://dl.dropbox.com/u/21717/ironruby-rc2.tar.bz2 if you want to build on mono and get a few launcher scripts you can use my linux branc

Re: [Ironruby-core] RCov

2010-03-08 Thread Jim Deville
Interesting to know though. Thanks for sharing! JD From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shri Borde Sent: Monday, March 08, 2010 11:14 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] RCov Just noticed that RCov can wo

Re: [Ironruby-core] RCov

2010-03-08 Thread Shri Borde
Just noticed that RCov can work in pure Ruby mode without the C-based core known as “rcovrt”. The pure Ruby mode is two orders of magnitude slower. Just FYI. There is still the issue that it will not profile .NET code… From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@ruby

Re: [Ironruby-core] IronRuby.Ruby.GetExecutionContext removed

2010-03-08 Thread Tomas Matousek
We removed it for 2 reasons: 1) RubyContext is not a supported public API and can change any time. Hosting APIs on the other hand (i.e. IronRuby.Ruby class) will remain stable. We'll try hard not to introduce breaking changes. 2) RubyContext is not remoting aware while Hosting APIs ar

Re: [Ironruby-core] IronRuby.Ruby.GetExecutionContext removed

2010-03-08 Thread Jimmy Schementi
By the way, if anyone is depending on IronRuby.Ruby.GetExecutionContex, your code will break when built/run against the HEAD of the sources. As a work-around, here's the implementation of GetExecutionContext which you can just use in your own code: using Microsoft.Scripting.Hosting;

Re: [Ironruby-core] IronRuby.Ruby.GetExecutionContext removed

2010-03-08 Thread Jimmy Schementi
Tomas, What reasons did we have for removing this in the first place? It also affects anyone writing code that uses our Ruby types/library methods in their own code (for providing the correct types to Ruby code); IronRuby.Rack does this. As a work-around, are we really expecting people to use