Ken Bloom wrote:
> In general, you should not rely on knowledge of the source code to
> understand how a library works, because the library writer reserves
> the right to change the behavior of things that are not specified in
> the documentation.

Ken - I certainly agree in theory.  However, in practice, that is often
the only way to understand most Ruby libs.  Ruby, as wonderful as it
is, has not reached the maturity where its libs come with stable,
complete documentation.

Check out libs like SOAP4R.  The source *is* the documentation.

Also, I would find linking to the source useful for libs which we are
developing in house.