"Ovid" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > --- Peter Scott <[EMAIL PROTECTED]> wrote: > > >The problem here is that it will not print inherited or AUTOLOADed methods. > > [snip] > > > > So traverse the inheritance hierarchy and do the same thing with each class: > > > > http://search.cpan.org/author/SBURKE/Class-ISA-0.32/ISA.pm > > That's certainly a decent 95% solution and if you *really* > need it, it's a good idea. The original problem, though, > is not one that I want to encourage most people to solve > because for most programmers, when things get that complicated, > it turns out that there's an underlying design flaw that needs > to be addressed. > > Of course, people seem to get mad when I say that :)
I'll second that. Absolutely. If you've created an object and are asking, 'Now what can I do with this object?' then you're not designing software, you're laying bricks. Find a module that, from the documentation, looks like it will do what you want. Then commit to using that module with the documented interface alone. After that, if you find you've made the wrong decision, be prepared to backtrack as far as necessary to redeem yourself. Software built on what a module /can/ do instead of what it's /supposed/ to do isn't a useful thing in any way. Rob -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
