>>>>> "PJ" == Paul Johnson <[EMAIL PROTECTED]> writes:
PJ> Some method of attaching a callback function to arbitrary opcodes would
PJ> be very useful.
how would you propose those callbacks be attached without op codes to do
the callback? :)
PJ> For example, in a code coverage tool a callback would be desirable
PJ> not only at the exit (or entry) of a block, or more accurately a
PJ> linear code sequence, but also at various points throughout a
PJ> conditional, so that it is possible to determine not only the
PJ> truth value of the conditional, but also why. As a trivial
PJ> example, in $x = $y || $z, was $y true, was it $z, or were they
PJ> both false?
i think that is best done with inserting special op codes when enabled
by a profiling or debug flag.
what dan is trying to do (and i am supporting) is keeping the dispatch
loop as small as possible. it is easier and faster to insert and
dispatch special op codes than to check more flags.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture and Stem Development ------ http://www.stemsystems.com
Learn Advanced Object Oriented Perl from Damian Conway - Boston, July 10-11
Class and Registration info: http://www.sysarch.com/perl/OOP_class.html
