MqMsgque_Setup_C_API

MqMsgque PACKAGE - setup und cleanup the ccmqmsgque … More...

Collaboration diagram for MqMsgque_Setup_C_API:

Functions
void	libmqmsgque::MqSetup (void)
	setup ccmqmsgque internal memory …
void	libmqmsgque::MqCleanup (void)
	cleanup ccmqmsgque internal memory …

Variables
bool	libmqmsgque::MqCleanupActive
	signal that code was triggert by libmqmsgque::MqCleanup

Detailed Description

MqMsgque PACKAGE - setup und cleanup the ccmqmsgque …

For details about MqSetup and MqCleanup usage refer to MkKernel_Setup_libmkkernel_C_API

Function Documentation

MqCleanup()

void libmqmsgque::MqCleanup

(

void

)

cleanup ccmqmsgque internal memory …

Cleanup will only be recognized once and will be ignored if not called in the same thread as Setup. After a call to Setup the call to MkCleanup is possible again.

1. By default, the public Cleanup with the gcc: __attribute__ ((cleanup(XXX))) is called when unloading the library.
2. The public Cleanup is only a placeholder and should not be used, the internal Cleanup is always called, even if the public Cleanup is not called.

Note

during cleanup objects will be deleted too -> the language interpreter have to be active

Here is the caller graph for this function:

MqSetup()

void libmqmsgque::MqSetup

(

void

)

setup ccmqmsgque internal memory …

Setup will only be recognized once, additional call's will be ignored until a Cleanup is called.

1. By default, the public Setup with the gcc: __attribute__ ((constructor(XXX))) is called when loading the library.
2. If the Target-Programming-Language (TPL) supports late loading of a shared library with dlopen and additionally uses threads, a manual call to Setup very early at startup is required to enforce the correct order of type declarations.

Here is the caller graph for this function:

Variable Documentation

MqCleanupActive

bool libmqmsgque::MqCleanupActive

extern

signal that code was triggert by libmqmsgque::MqCleanup