Re: Import gem to Ruby 1.9

In article <[e-mail]>,
  "NAKAMURA, Hiroshi" <[e-mail]> writes:

> 2. allow gem method to work.  And gem method is usable always.  With
> yours, it depends on a context of previous LoadError whether a library
> can use gem method or not.  I don't like this statefullness, too.

In the IRC session, drbrain said that separating Kernel.gem
to independent library is possible.  (matz asked it.)

So my tiny loader will load RubyGems without gem method.
The statefullness will be removed.

> 1. does not have uncertain behavior.  No require 'doc/index' problem I
> wrote at [ruby-core:12792].

I agree that mine is not accurate as yours or RubyGems
itself.

In contrast, the disadvantage of yours are memory
consumption and maintenance.

I think maintenance is critical problem.  Your gemloader.rb
is not appropriate for incorporating to Ruby until some
maintainer available.

The accuracy and memory consumption is trade off.  For
accuracy, all gemspecs must be loaded and analyzed.  But it
consumes memory: analyzer code and loaded gemspecs.

Since RubyGems itself does accurate analysis, its loader can
be conservative.  I think memory consumption justify the
conservativeness.

> Your proposal of prelude.rb enables RubyGems.  As I wrote, RubyGems uses
> their 'version selection scheme' independent from whether gem method
> exists or not.  So you cannot use any other scheme.  RUBYOPT solution
> allow you to do the above.

I can install any library under site_ruby.  Does RubyGems
prohibit it?
-- 
Tanaka Akira