I'd rather not have to switch to /Zi (Program Database) and lose Edit & Continue.
For example:
#define _STR2_(x) #x
#define _STR1_(x) _STR2_(x)
TRACE(_STR1_(__LINE__));
Instead of a numeric value I get "(__LINE__Var+1)".
With VS2005, I tried dropping your macros into an mfc dialog based app (ONOK handler) as follows:
#define _STR2_(x) #x #define _STR1_(x) _STR2_(x) void CmfcfooDlg::OnBnClickedOk() { TRACE(_STR1_(__LINE__)); TRACE("\n"); OnOK(); } And the debugger shows me the line number as expected. Do you have a small repro you could share? My email address shows in the profile.
RickTroemelMS at 2007-9-8 >
I read your post more closely and realized you are using VS2003 and are likely referring to the bug in the KB article at http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b199057.
The good news is that the problem is corrected in VS2005, the bad is that there is no other workaround besides switching to /Zi.
One suggestion I could make - if you are using __LINE__ to generate a unique identifier, __COUNTER__ may work for you.
Hope This Helps,
One of my uses for __LINE__ is to generate trace output that can be double-clicked in the Visual Studio output window to jump to the appropriate source file/line number. __COUNTER__ won't work in this case.
