Diagnostics.h File Reference

#include <Imt.Base.Core.Platform/Platform.h>
#include "AssertActionManager.h"
#include <Imt.Base.Core.Diagnostics/DiagnosticsConfigApp.h>

Functions
void	ASSERT_EX1 (bool const condition, char_t const *const pMessage)
	"Assert and throw exception" (ASSERT_EX). More...
void	ASSERT_EX (bool const condition)
void	ASSERT_DEBUG1 (bool const condition, char_t const *const pMessage)
	"Assert for debugging only" (ASSERT_DEBUG). More...
void	ASSERT_DEBUG (bool const condition)

Function Documentation

ASSERT_DEBUG()

void ASSERT_DEBUG ( bool const  condition )

inline

See also

ASSERT_DEBUG1

ASSERT_DEBUG1()

void ASSERT_DEBUG1 ( bool const  condition, char_t const *const  pMessage  )

inline

"Assert for debugging only" (ASSERT_DEBUG).

Use this sort of assertion only while debugging. This flavor of asserts will be compiled only for a debug build on the the developer machine and on the target as well.

Parameters

condition	When this condition evaluates to false the handler will be called
pMessage	The message to specify the error that has occurred

ASSERT_EX()

void ASSERT_EX ( bool const  condition )

inline

See also

ASSERT_EX1

ASSERT_EX1()

void ASSERT_EX1 ( bool const  condition, char_t const *const  pMessage  )

inline

"Assert and throw exception" (ASSERT_EX).

Even so we do not have exception support use this macro to test conditions for which it is not secure to continue safely when the condition evaluates to false. The registered handler is responsible to react appropriately. There is a second version of this macro with a postfix of 1. It takes additionally a second parameter. This parameter is for future extensions in the debugging environment. It takes a c-string which will be used to indicate the reason of the failure.

Parameters

condition	When this condition evaluates to false the handler will be called
pMessage	The message to specify the error that has occurred