#include <basis/astring.h>

Include dependency graph for critical_events.h:

Classes
class	loggers::critical_events
	Provides a means of logging events for runtime problems. More...

Namespaces
	loggers
	A logger that sends to the console screen using the standard output device.

Macros
#define	CAUSE_BREAKPOINT
	This macro wraps the notion of stopping in the debugger. More...

#define	REQUIRE(check) if (!check) CAUSE_BREAKPOINT;
	Tests the value "check" to ensure that it's not zero. More...

#define	non_continuable_error(c, f, i)
	an extra piece of information used, if available, in bounds_halt below. More...

#define	continuable_error(c, f, i)

#define	console_error(c, f, i) critical_events::FL_console_error(__FILE__, __LINE__, c, f, i)

#define	deadly_error(c, f, i) critical_events::FL_deadly_error(__FILE__, __LINE__, c, f, i)

#define	out_of_memory_now(c, f) critical_events::FL_out_of_memory_now(__FILE__, __LINE__, c, f)

Macro Definition Documentation

◆ CAUSE_BREAKPOINT

#define CAUSE_BREAKPOINT

This macro wraps the notion of stopping in the debugger.

Definition at line 24 of file critical_events.h.

◆ console_error

#define console_error	(	c,
		f,
		i
	)	critical_events::FL_console_error(__FILE__, __LINE__, c, f, i)

Definition at line 85 of file critical_events.h.

◆ continuable_error

#define continuable_error	(	c,
		f,
		i
	)

Value:

critical_events::FL_continuable_error(__FILE__, __LINE__, c, f, i, \

"Runtime Problem Information")

eml_to_txt.f

f

Definition: eml_to_txt.py:143

Definition at line 82 of file critical_events.h.

◆ deadly_error

#define deadly_error	(	c,
		f,
		i
	)	critical_events::FL_deadly_error(__FILE__, __LINE__, c, f, i)

Definition at line 87 of file critical_events.h.

◆ non_continuable_error

#define non_continuable_error	(	c,
		f,
		i
	)

Value:

critical_events::FL_non_continuable_error(__FILE__, __LINE__, c, f, i, \

"A Non-Continuable Runtime Problem Has Occurred")

an extra piece of information used, if available, in bounds_halt below.

Verifies that "value" is between "low" and "high", inclusive.

"Value" must be an object for which greater than and less than are defined. The static_class_name() method and func definition are used to tag the complaint that is emitted when problems are detected. Note that if CATCH_ERRORS is defined, then the program is halted if the value is out of bounds. Otherwise, the "to_return" value is returned. Provide some macros that will automatically add the file and line number.

These use the functions below to report different types of error situations and in some cases, exit the program.

Definition at line 79 of file critical_events.h.

◆ out_of_memory_now

#define out_of_memory_now	(	c,
		f
	)	critical_events::FL_out_of_memory_now(__FILE__, __LINE__, c, f)

Definition at line 89 of file critical_events.h.

◆ REQUIRE

#define REQUIRE ( check ) if (!check) CAUSE_BREAKPOINT;

Tests the value "check" to ensure that it's not zero.

This can be used instead of an ASSERT macro to check conditions in builds with ERRORS_ARE_FATAL turned on. This macro is orthogonal to the build being built with debugging or release features.

Definition at line 46 of file critical_events.h.

Classes

Namespaces

Macros