question about __FUNCTION__ and __FILE__

[ptclin_2007]

i can use __FUNCTION__ and __FILE__to debug in vc,

does carbide can use these?

if can how to do?

[qxiaoyuan]

yes, the macro is defined in vc or carbide, gcce compiler, etc.

use as normal macro. like

class CFuncTrace
{
public:
    CFuncTrace(const char* file, const char* func, int line)
    {
        iFile = (const TUint8*)file;
        iFunc = (const TUint8*)func;
        iLine = line;
        LOG_FMT( KFuncTraceEnterFormat, &iFile, &iFunc, iLine );
    }
    
    ~CFuncTrace()
    {
        LOG_FMT( KFuncTraceLeaveFormat, &iFile, &iFunc, iLine );
    }

private:
    CFuncTrace(const CFuncTrace&);
    CFuncTrace& operator= (const CFuncTrace&);
    
private:
    TBuf8<100>      iFile;
    TBuf8<100>      iFunc;
    int             iLine;
};


#define FUNC_TRACE(name)            CFuncTrace name(__FILE__, __FUNCTION__, __LINE__)
#define FUNC_U_TRACE()              CFuncTrace _func_trace_(__FILE__, __FUNCTION__, __LINE__)

[ptclin_2007]

thanks!

i wrote const char* tc = __FILE__ ;
and compiled error,prompt crosses initialization of `const char*tc'

what should do?

[skumar_rao]

refer to all usages in http://developer.symbian.com/wiki/di.../Useful+macros

[savaj]

i wrote const char* tc = __FILE__ ;
and compiled error,prompt crosses initialization of `const char*tc'

Statement const char* tc = __FILE__; looks fine to me. I am wondering why its gives you a initialization error.

[wizard_hu_]

What is the exact error message you get? Where have you written that line?