AliRoot Core  edcc906 (edcc906)
AliFMDDebug.h File Reference
#include <AliLog.h>
Include dependency graph for AliFMDDebug.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

## Macros

#define AliFMDDebug(N, A)

## Macro Definition Documentation

 #define AliFMDDebug ( N, A )
Value:
do { \
AliLog::GetDebugLevel(MODULENAME(), ClassName()) < N) break; \
AliLog::Debug(N, Form A, MODULENAME(), ClassName(), FUNCTIONNAME(), \
__FILE__, __LINE__); } while (false)
#define FUNCTIONNAME()
Definition: AliLog.h:198
Definition: AliLog.h:27
static Bool_t IsDebugEnabled()
Definition: AliLog.h:91
#define MODULENAME()
Definition: AliLog.h:189
static Int_t GetDebugLevel(const char *module, const char *className)
Definition: AliLog.cxx:843

AliFMDDebug

Parameters
 N Debug level - always evaluated A Argument (including paranthesis) to Form - the message to print. Note, that A should contain balanced paranthesis, like  AliFMDDebug(1, ("Failed to decode line %d of %s", line, filename));  The point is, if the current log level isn't high enough, as returned by the AliLog object, then we do not want to evalute the call to Form, since that is an expensive call. We should always put macros like this into a do ... while loop, since that makes sure that evaluations are local, and that we can safely put a ; after the macro call. Note, that do ... while loop and the call with extra paranthis, are an old tricks used by many C coders (see for example Bison, the Linux kernel, and the like).

Definition at line 39 of file AliFMDDebug.h.