Next: conditions signal two, Previous: conditions signal, Up: conditions [Contents][Index]
We can use the signal–1 exceptional–condition object–type to signal some special test condition. We can instantiate this type and also derive new types from it. To catch this exceptional condition we can do:
cce_location_t L[1]; if (cce_location(L)) { if (cctests_condition_is_signal_1(cce_condition(L))) { CCTESTS_PC(cctests_condition_signal_1_t, C, cce_condition(L)); do_something_with(C); } cce_run_catch_handlers_final(L); } else { do_something(L); cce_run_body_handlers(L); }
Type of data structure representing the exceptional–condition descriptor. It has the following public fields:
cce_descriptor_t descriptor
The condition descriptor’s base values.
The parent of this type descriptor is the one referenced by cctests_descriptor_signal_ptr
,
Convenience signal.
Type of data structure representing the exceptional–condition object. It has the following public fields:
cctests_condition_signal_t signal
The condition object’s base values.
Set the parent of the descriptor referenced by D to the descriptor of the
exceptional–condition object–type cctests_condition_signal_1_t
.
Initialisation function for the condition object. This function is meant to be called from the
initialisation function of sub–types of cctests_condition_signal_1_t
.
Return a pointer to exceptional–condition object of type
cctests_condition_signal_1_t
made opaque in the type cce_condition_t
.
Return true
if C if of type cctests_condition_signal_1_t
; otherwise
return false
.
To define a sub–type of cctests_condition_signal_1_t
we can copy the code in the files:
condition-signal-1-subtype.c condition-signal-1-subtype-headear.h condition-signal-1-subtype-body.c
under the tests directory of the source distribution; the code defines a new
condition–object type my_condition_signal_1_subtype_t
.
Next: conditions signal two, Previous: conditions signal, Up: conditions [Contents][Index]
This document describes version 0.4.1-devel.1 of CCTests.