==============================================================================
- Release of version 0.02 of NEXT
+ Release of version 0.50 of NEXT
==============================================================================
the current class -- to look for a suitable method in other
ancestors of C<$self> -- whereas C<$self->SUPER::m()> cannot.
- An particularly interesting use of redispatch is in
+ A particularly interesting use of redispatch is in
C<AUTOLOAD>'ed methods. If such a method determines that it is
not able to handle a particular call, it may choose to
redispatch that call, in the hope that some other C<AUTOLOAD>
(above it, or to its left) might do better.
- Note that it is a fatal error for any method (including C<AUTOLOAD>)
- to attempt to redispatch any method except itself. For example:
-
- sub D::oops { $_[0]->NEXT::other_method() } # BANG!
+ The module also allows you to specify that multiply inherited
+ methods should only be redispatched once, and what should
+ happen if no redispatch is possible.
AUTHOR
==============================================================================
-CHANGES IN VERSION 0.02
+CHANGES IN VERSION 0.50
+
+
+ - Added a $VERSION (oops!)
+
+ - Fixed handling of diamond patterns (thanks Paul)
+
+ - Added NEXT::ACTUAL to require existence of next method (thanks Paul)
+ - Added NEXT::UNSEEN to avoid calling multiply inherited
+ methods twice (thanks Paul)
- - Fixed setting of $AUTOLOAD in NEXT'd AUTOLOADS (thanks Leonid)
+ - Re-fixed setting of $AUTOLOAD in NEXT'd AUTOLOADS to be
+ consistent with more useful SUPER:: behaviour
- - Changed licence for inclusion in core distribution
+ - Corified tests
==============================================================================