Tomas - The problem seems to be coming from rubygems/custom_required.rb. It
redefines Kernel.required() and is not re-throwing the error properly:
This works:
module Kernel
alias gem_original_require require # :nodoc:
def require(path) # :nodoc:
gem_original_require path
end
end # mo
I see. Well it seems more broken than I thought it is :)
Tomas
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Turpin, Jay
Sent: Tuesday, September 23, 2008 9:37 AM
To: 'ironruby-core@rubyforge.org'
Subject: Re: [Ironruby-core] question on RubyGems
Tomas - Thanks for the advice. H
Tomas - Thanks for the advice. However, it is still not working as expected.
When I run this ruby script:
require 'rubygems'
require 'rake'
puts $LOAD_PATH
It give me this output:
C:\temp>ir -D t.rb
C:/Projects/IronRuby/lib/ruby/site_ruby/1.8\rubygems/custom_require.rb:31:in
`require': Bogus
Note that "rbd" is an alias for "ir -D" on my machine ;)
Tomas
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tomas Matousek
Sent: Tuesday, September 23, 2008 9:30 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] question on RubyGems
-D is actually what you need:
-D is actually what you need:
C:\Temp>rbd x.rb
C:\M1\ndp\fx\src\Core\Microsoft\Scripting\Actions\CallSite.cs:275:in
`UpdateAndExecute'
C:\M1\ndp\fx\src\Core\Microsoft\Scripting\Actions\UpdateDelegates.Generated.cs:38:in
`Update2'
x.rb:7:in `bar'
C:\M1\ndp\fx\src\Core\Microsoft\Scripting\Actions\
Michael - Thanks for the quick response, but that's not quite what I meant.
When I run Ruby and get an error, I get the complete stack trace of the Ruby
code:
C:\temp>ruby t.rb
c:/ruby/lib/ruby/site_ruby/1.8/rubygems/version.rb:283:in `satisfy?': Bogus
Error (RuntimeError)
from c:/ruby/
You can also use tracing proc:
Hook it in a code:
set_trace_func proc { |*a|
p a
}
and run ir.exe with -trace option.
Note that stack traces are not available in -X:Interpret mode yet and in
compiled mode they contain some internal frames. It's the next item in my TODO
list to fix that.
Tom
-D should give you script line numbers on the stack trace.
On Tue, Sep 23, 2008 at 8:42 AM, Jay Turpin <[EMAIL PROTECTED]> wrote:
> I did some research into getting rubygems and rake to work in IronRuby.
> The first thing I had to do was set the ENV variable GEM_PATH to the
> IronRuby/lib/ruby/ge
I did some research into getting rubygems and rake to work in IronRuby.
The first thing I had to do was set the ENV variable GEM_PATH to the
IronRuby/lib/ruby/gems/1.8 directory. That enabled rubygems to at least
locate the rake gem.
But now I'm stuck on an possible issue in the rubygems librar
