in reply to Re: AUTOLOAD does not scale
in thread OO Inheritence
it is perfectly possibly
Remove "perfectly" from that sentence and I'll agree with you. From NEXT's documentation:
Because it's a module, not an integral part of the interpreter, NEXT.pm has to guess where the surrounding call was found in the method look-up sequence. In the presence of diamond inheritance patterns it occasionally guesses wrong.
It's also too slow (despite caching).
I repeat what I've said earlier, that using AUTOLOAD may very well cause you a bigger problem than the one you tried to solve. (Re: is autoload bad style?)