From: [EMAIL PROTECTED] (Martin A. Hansen)
> a bricklayer! so i have found a module which is fulfilling my needs,
> but i find it very annoying that i cannot simple dump all the
> functions connected to a certain object. now im advised to read the
> module documentation (which can be poor) of this object, AND the
> module documentation of ALL inherited objects!
Apart from the Net::... and HTTP:: messes deep hierarchies are pretty
uncommon in the Perl world. And if the documentation of a module is
poor, most likely the code will be as well.
> but enough nagging. even if this is a tricky problem, cant it be
> solved? if using the ISA.pm as suggested, you are able to track the
> inheritance solving 95% of the problem, then what is the remaining 5%
> ?
No. I mean the more you try to nearer to 100% you'll get, but it'll
never be 100%. You can't prevent the module authors to be creative
with autoloading and autodefinig.
Guess what methods does this object support ;-)
package Len;
sub new {
my $self;
bless \$self, 'Len';
}
sub AUTOLOAD {
$AUTOLOAD =~ s/^.*:://;
return length($AUTOLOAD);
}
Jenda
===== [EMAIL PROTECTED] === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed
to get drunk and croon as much as they like.
-- Terry Pratchett in Sourcery
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
