Define some macros to facilitate the call stack tracing

[GoogleCodeExporter]

In order to reduce the risk of writing things wrong and guarantee that there 
will be some consistency, it is necessary to create some macros which simplify 
the task of writing call stack traces at the beginning of functions. There will 
be 3 kinds of macros with up to 8 parameters, called as follows:

QE_TRACE_CALLSTACK_FUNCTION_*PARAMS(strFunctionSignature, param1, param2, etc.)
QE_TRACE_CALLSTACK_METHOD_*PARAMS(strClassName, strMethodSignature, param1, 
param2, etc.)
QE_TRACE_CALLSTACK_OBJECT_METHOD_*PARAMS(strMethodSignature, param1, param2, 
etc.)

Where * is a number from 0 to 8. In total, 27 macros.
It is important to take alook to the /team/CallStackTracer project, 
CallStackTacer.cpp file.

Original issue reported on code.google.com by Lince3D@gmail.com on 7 May 2014 at 1:09

• Blocked on: #577

[GoogleCodeExporter]

Original comment by Lince3D@gmail.com on 14 Nov 2014 at 12:01

• Added labels: Phase-3
• Removed labels: Phase-2

[GoogleCodeExporter]

Add macros for choosing QArgument constructor overload:
QE_PARAM_HAS_TOSTRING
QE_PARAM_HAS_GETTYPE
QE_PARAM_HAS_GETTYPE_TOSTRING

Original comment by Lince3D@gmail.com on 13 Jan 2015 at 11:28

[GoogleCodeExporter]

Original comment by Lince3D@gmail.com on 22 Jan 2015 at 3:52

• Changed state: New

[GoogleCodeExporter]

Original comment by Lince3D@gmail.com on 22 Jan 2015 at 5:59

• Changed state: Started

[GoogleCodeExporter]

Original comment by Lince3D@gmail.com on 23 Jan 2015 at 5:39

• Changed state: Done