Jan Kiszka wrote:
 > Gilles Chanteperdrix wrote:
 > > bheap_destroy allow
 > > setting the bheap_t structure to an invalid value which, in turn, allow
 > > helping upper layers in catching invalid uses of the bheap after its
 > > destruction.
 > Ok, we could make bheap_destroy pop up under XENO_OPT_DEBUG. We may then
 > also add assertions to the bheap functions themselves to check for
 > invalid usage.

The checkings are already there, if you do not remove
bheap_destroy. They are unconditionnal, because I find such checkings way
too important to be optimized out.


                                            Gilles Chanteperdrix.

Xenomai-core mailing list

Reply via email to