A quick followup...

Jim Weirich wrote:
> -- Using 0.8.11 -----------
> 
> $ gem -v
> 0.8.11
> $ irb
> irb(main):001:0> require 'a'
> Loading B
> Loading A
> => true
> irb(main):002:0>

Note that you only get this behavior when the b package specifies an 
autorequire file (which b does in this case, and which the fastercsv 
package does as well).  When RubyGems activates b, it does any 
autorequires specified by b.

This is why:

(1) I really believe autorequire is evil.  It isn't the only subtle bug 
it has caused.
(2) The soon to be released RubyGems removes a lot of the autorequire 
behavior.

-- Jim Weirich

-- 
Posted via http://www.ruby-forum.com/.