It should work as soon as we push the latest source out.
Tomas
From: [email protected]
[mailto:[email protected]] On Behalf Of Thibaut Barrère
Sent: Saturday, January 30, 2010 5:10 AM
To: ironruby-core
Subject: [Ironruby-core] Differences between 1/ MRI and 2/ IronRuby+JRuby
Hello,
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'
from binding-error.rb:19
(erb):1: undefined method `version' for main:Object (NoMethodError)
from C:/IronRuby/lib/ruby/1.8/erb.rb:716:in `result'
from binding-error.rb:19
from :0:in `eval'
It's just like values.send(:binding) is doing nothing.
any thoughts ?
thanks,
-- Thibaut
--- Begin Message ---
tfpt review "/shelveset:bindingandyamlfxcop;REDMOND\tomat"
Comment :
Kernel#binding captures receiver and eval uses it as "self".
Adds FxCop configuration to yaml .csproj.
Tomas
bindingandyamlfxcop.diff
Description: bindingandyamlfxcop.diff
--- End Message ---
_______________________________________________
Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core