in reply to chaining callbacks

Since you've already precluded my first thought (derived class implementation), how about a left field idea? Have the call back die with some "I don't do this stuff" string or object and have the call back caller figure it out. That way return results and normal execution are unaffected by the handling mechanism used for managing call back processing.

True laziness is hard work

Replies are listed 'Best First'.
Re^2: chaining callbacks
by John M. Dlugosz (Monsignor) on May 07, 2011 at 07:04 UTC
    I like the idea of separating out-of-band control returns from the normal return of a value. Perhaps this would be a good approach for Perl 6. But exceptions are too expensive and not intended as a "normal" control-flow mechanism.