There's no sence to subclasse a module that doesn't have the architecture that will do what you want. For example, there's no module, before lib::http, that with just the Perl CORE I can use other libraries in other location. This is not just about code and interface, is also about what happens in the background.

In reply to Re^4: lib::http - Using virtually a Perl library from the Internet with the HTTP protocol. by Anonymous Monk
in thread lib::http - Using virtually a Perl library from the Internet with the HTTP protocol. by gmpassos

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":