Loading rdoc in a ruby script leads to a conundrum of sorts.
This will load the version of RDoc distributed with Ruby. But it is a
very old version. Installing the latest version of RDoc via gem
however doesn’t help either. It still loads Ruby’s distributed version
b/c RubyGems lets Ruby try to load a lib first, and only looks for it
in the installed gems if that fails. Thus the only way to get the
latest version of RDoc is to use.
But as we all know that is not a good practice --in the advent that
another load system is being used. I work around it with some error
caching code, of course, But that doesn’t answer the open issue that
3rd party libraries distributed with Ruby can fail to load properly if
a later version is installed via another means such as RubyGems.
My first thought for a solution is that RubyGems should search for the
file first, rather then let Ruby try and fail before doing so. And I
think Ruby 1.9 basically does exactly that by by putting all the
latest gems automatically put on the load path (although I here there
is an issue with this as well at
GitHub - wycats/rubygems-bug-demo).
However, this is very inefficient. Consider loading ‘ostruct.rb’ –
does it really need to search through every installed gem first before
finally picking ostruct.rb up from Ruby itself?
So I’m a starting to think that Ruby could use a distinction between
standard libs and redistributed libs, and provide a way to look them
up separately. This way RubyGems could set things up to search Ruby’s
standard libs first, then the gems, then Ruby’s redistributed libs.