During a test, it is often desired to have the possibility to execute a portion of BDL code in reaction to one or more particular situations / events. Creating such a portion of BDL code is made easy by using an event handler function. A typical task of an event handler is to e.g. perform clean-up statements after a transaction exit error, or generally catch an error or warning before it gets reported. EVENT_TRANS_END (Transaction end (within transaction context)) is included as part of the transaction and therefore any actions affect timings for the transactions. EVENT_TRANS_FINISHED (Transaction finished (not within transaction context)) occurs once the transaction is over and any actions are not included in the transaction. This is what is meant by context. You can see this in the order of print statements for the following handlers: dclevent handler Handler1 begin Print( "Waiting in Trans End" ); Wait ( 1.0 ); throw ; end Handler1; handler Handler2 begin Print( "Waiting in Trans Finished" ); Wait ( 1.0 ); throw ; end Handler2; Output: For more information on Event Handlers please see the "Event handler section overview" in SilkPerformer Help. Old KB# 17962
↧