16 Jun
2013
16 Jun
'13
4:26 p.m.
Sorry. I've misinterpreted MSVC output. I do see the error now. And... this
is really weird one. I did not see something like this in a long time. What it comes to can be illustrated in this example:
So if I understand, we are actually dealing with a compiler issue here regarding the proper resolution of namespaces. Is that what you are saying?
If that is the case, you need a file a bug on http://connect.microsoft.com, or use the VS 2012 Feedback Tool to report the problem from inside VS 2012: http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c...
OK. I will look into it this week. I will report back with any tangible reproducible bug report that may arise. Sincerely, Chris.