NAME
SET_CANT_HAPPEN_BUG - (MACRO) Sets up call to set_bug
SYNOPSIS
#include "l/l_sys_err.h"
Example compile flags (system dependent):
-DLINUX_386 -DLINUX_386_P4
-I/home/kobus/include
-L/home/kobus/load/linux_386_p4 -L/usr/local/lib -L/usr/lib
-lKJB -llapack -lblas -lg2c -lXext -lX11
void SET_CANT_HAPPEN_BUG(void);
DESCRIPTION
This macro sets up the call to set_bug when a problem can be described as
an attempt to execute code which in theory cannot be executed. In
development code (i.e. when TEST is defined), a generic message this
condition is passed to the routine set_bug() together with the file and line
number. In non-development code, a more user oriented message is passed
(depending on the setting of the symbol REPORT_ALL_BUG_INFO). Note that the
behaviour of set_bug() itself is dependent on the bug_handler, and the
behaviour default bug handler is dependent on whether or not the code is
development code.
Note :
It is advisable to expect SET_CANT_HAPPEN_BUG to return, even though
under many circumstances it will not. Normally the statement after
SET_CANT_HAPPEN_BUG is an error return.
SEEALSO
set_bug, set_bug_handler, default_bug_handler
DISCLAIMER
This software is not adequatedly tested. It is recomended that
results are checked independantly where appropriate.
AUTHOR
Kobus Barnard
DOCUMENTOR
Kobus Barnard
SEE ALSO
SET_BUFFER_OVERFLOW_BUG
,
SET_FORMAT_STRING_BUG
,
SET_ARGUMENT_BUG
,
SET_BOUNDS_BUG
,
SET_SORT_BUG
,
SET_OVERFLOW_BUG
,
SET_UNDERFLOW_BUG