From: Roger Pack <rogerpack2005@...>
Date: 2009-11-15T14:50:51+09:00
Subject: Re: Ruby Inline over two times slower under 1.9 than under 1.8?

>> here's a working example (well worked once upon a time).
>> http://betterlogic.com/roger/?p=1849
> 
> $ gem which ruby_to_ruby_c
> (checking gem RubyToC-1.0.0.5 for ruby_to_ruby_c)
> /home/shot/opt/ruby-1.8.7-svn/lib/ruby/gems/1.8/gems/RubyToC-1.0.0.5/lib/ruby_to_ruby_c.rb
> 
> Fortunately, I noticed the 1.0.0.5 version not
> matching 1.0.0.7 in the example and cd-ed to
> /home/shot/opt/ruby-1.8.7-svn/lib/ruby/gems/1.8/gems/ruby2c-1.0.0.7
> instead. Still, with RubyToC being higher on the gem searchpath (?):
> 
>>> RubyParser.new.parse(File.read 'hello.rb')
> NoMethodError: undefined method `clear' for nil:NilClass

Hmm. Maybe a bug in ruby parser?


> After uninstalling RubyToC (and, I assume, ruby_parser falling back
> to ruby2c) the above blog example works, both in 1.8.7-p202+r22308
> and 1.9.1-p243+r22308. Is there a ‘conflicts’ flag for gems, so that
> ruby_parser can specify that it (as far as I understand) works with
> ruby2c 1.0.0.7 but not with RubyToC 1.0.0.5?

So RubyToC 1.0.0.5 only works with an older version of ruby_parser, is 
that right?
-r
-- 
Posted via http://www.ruby-forum.com/.