Re: VC++ 2008 compiler bug
Amal wrote:
On Feb 22, 12:57 pm, Amal <amal.paramb...@gmail.com> wrote:
On Feb 22, 11:11 am, "Carl Daniel [VC++ MVP]"
<cpdaniel_remove_this_and_nos...@mvps.org.nospam> wrote:
Amal wrote:
So there is no confusion that it is a bug inside the Microsoft
compiler.
So it would appear. Help the VC++ community by creating a bug
report athttp://connect.microsoft.com/VisualStudio/Feedback. If
you post the URL to the bug report back to this thread, others can
validate and/or vote for your
bug.
-cd
I reported it long back but Microsoft didn't felt it is a bug to be
fixed.
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx...
This is a link to the issue I reported earlier.
Thanks,
Amal P
Anyway I have reported the bug again. The link is,
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=329612
OK, I did.
A couple things to understand relevant to your original bug report:
- The C++ compiler is used to build the rest of Visual Studio, so the C++
team stops taking changes very early in the release cycle compared to other
teams. In the case of Orcas (VS2008), when you submitted your bug
originally, the C++ team been deferring or rejecting taking all but critical
bugs for about 3 months.
- When a bug like this is closed as "Won't Fix", it doesn't mean "won't ever
fix", it means "won't fix in current product cycle". Some time between
releases, they'll review all closed bugs and many of them will be re-opened
for work in the next product cycle.
- If this issue is causing you problems, you should contact product support.
They may or may not be able to help you in the short term, but having the
issue raised through PSS adds weight to the bug and increases the likelihood
of it being fixed sooner. Requesting a fix through PSS is the only way that
a hotfix or service pack will ever include a fix for your bug - otherwise,
the next major release is the first opportunity.
-cd