[Ironruby-core] Differences between 1/ MRI and 2/ IronRuby+JRuby
jdeville at microsoft.com
Mon Feb 1 13:16:38 EST 2010
We should be doing an MSI in the next few weeks.
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Thibaut Barrère
Sent: Monday, February 01, 2010 9:02 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Differences between 1/ MRI and 2/ IronRuby+JRuby
> It should work as soon as we push the latest source out.
thanks for the update (note that I'm in no hurry on these bugs - I'm just pushing what I find as I go, based on the MSI release, and using workaround whenever necessary).
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 Thibaut Barrère
Sent: Saturday, January 30, 2010 5:10 AM
Subject: [Ironruby-core] Differences between 1/ MRI and 2/ IronRuby+JRuby
maybe someone can shed some light on that - the question is: is there a setting to make IronRuby works the same way MRI Ruby does by default for what I'm describing below ? I don't think it's a bug (but well maybe it is, just wondering).
Using this script http://gist.github.com/290538 , MRI has a different behaviour than JRuby or IronRuby.
The script will work just fine in MRI, whereas in JR/IR you'll get:
(erb):2: undefined local variable or method `version' for main:Object (NameError)
from :1:in `eval'
from /opt/local/share/java/jruby/lib/ruby/1.8/erb.rb:743:in `result'
(erb):1: undefined method `version' for main:Object (NoMethodError)
from C:/IronRuby/lib/ruby/1.8/erb.rb:716:in `result'
from :0:in `eval'
It's just like values.send(:binding) is doing nothing.
any thoughts ?
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