C
Chris Stankevitz
Hi all,
I once had a function in which I could not set a breakpoint. VS VC++ .net
2003 7.1 (native c++) would crash. This particular function had about five
arguments. Each argument was an STL container of some sort. The "expanded"
name of the function (with all templates written out) was extrememly large
and I believe this was the cause of the crash. I worked around the problem
by creating a "dummy" struct to hold the five arguments.
I previously thought these warnings could be ignored:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\vector(152) :
warning C4503: 'std::allocator<_Ty>::rebind<_Other>' : decorated name length
exceeded, name was truncated
However, my experience with this crash is leading me to rethink this
approach.
What should I do about C4503? The GCC build of my project has a "no
warnings tolerated" policy, but the MSVC 7.1 .net 2003 build has the
"luxury" of C4503 warnings. Can I safely ignore them?
Thanks for your input,
Chris
I once had a function in which I could not set a breakpoint. VS VC++ .net
2003 7.1 (native c++) would crash. This particular function had about five
arguments. Each argument was an STL container of some sort. The "expanded"
name of the function (with all templates written out) was extrememly large
and I believe this was the cause of the crash. I worked around the problem
by creating a "dummy" struct to hold the five arguments.
I previously thought these warnings could be ignored:
C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\vector(152) :
warning C4503: 'std::allocator<_Ty>::rebind<_Other>' : decorated name length
exceeded, name was truncated
However, my experience with this crash is leading me to rethink this
approach.
What should I do about C4503? The GCC build of my project has a "no
warnings tolerated" policy, but the MSVC 7.1 .net 2003 build has the
"luxury" of C4503 warnings. Can I safely ignore them?
Thanks for your input,
Chris