in reply to Re^4: Is "ref($class) || $class" a bad thing?
in thread Is "ref($class) || $class" a bad thing?

I'd consider that "a bit too much navel inspection". It breaks code I write that looks like this:
my $destiny = $someobject->can("somemethod"); @_ = ($someobject, @args); goto &$destiny;
There shouldn't be any way that this target method should be able to tell that I got there with ->can instead of a true method lookup. So if you write code that breaks that, shame on you.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

Replies are listed 'Best First'.
Re^6: Is "ref($class) || $class" a bad thing?
by adrianh (Chancellor) on Jul 20, 2004 at 16:46 UTC
    I'd consider that "a bit too much navel inspection"

    Oh I agree completely (I said I was surprised that nobody had mentioned it - not that it was a good idea :-)

    It breaks code I write that looks like this:

    ++ Good point.