Prev: Endianness of padded scalar objects - Correction
Next: Click in the command prompt window pauses the application
From: Darko Miletic on 26 Feb 2010 07:35
Mycroft Holmes wrote:
> On Feb 25, 3:40 pm, David Lowndes <Dav...(a)example.invalid> wrote:
>>> we have a large template-based set of headers; they are pretty much
>>> standard compliant and we cross-compile with VS2005, VS2008, the intel
>>> compiler and some versions of gcc. A few days ago we tested VS2010 RC
>>> and we found the following problems:
>> If you feel fairly certain it's a bug, please submit it on the MS
>> connect web site - that way MS will be aware of it.
>>
>> Dave
>
> I continuously forget the link for bug submissions... can you repost
> it here?
> TIA
> --mh

https://connect.microsoft.com/VisualStudio
From: Michael Goldshteyn on 3 Mar 2010 09:59
"Mycroft Holmes" <psion.s5(a)gmail.com> wrote in message
news:9812cb54-c21d-4f44-b581-9e17df8a0052(a)15g2000yqa.googlegroups.com...
> Hi all,
>
> we have a large template-based set of headers; they are pretty much
> standard compliant and we cross-compile with VS2005, VS2008, the intel
> compiler and some versions of gcc. A few days ago we tested VS2010 RC
> and we found the following problems: ...

Wow! MS is refusing to fix this bug, saying it does not meet their "triage
bar." I would strongly recommend that anyone who uses the Visual C++
compiler go to the following link and up-vote this bug so that it gets fixed
before VS 2010 RTM is released:

https://connect.microsoft.com/VisualStudio/feedback/details/536430/visual-studio-2010-compiler-bug-pointer-to-overloaded-member-function-with-t

Here is their reply on MS connect:

-----
Hi: I can confirm that this is a bug with Visual C++. Unfortunately it does
not meet the triage bar for the current release of Visual C++ - but we will
keep the issue in our database and we will look at it again during the
development phase of a future release of Visual C++.

Jonathan Caves
Visual C++ Compiler Team
-----


From: David Lowndes on 3 Mar 2010 10:23
>Wow! MS is refusing to fix this bug, saying it does not meet their "triage
>bar."

That darned bar is a real obstacle to jump over. I hate it ;)

>Here is their reply on MS connect:

At least you've had a reply from the man who'll probably get round to
fixing it as soon as he's allowed to :)

Dave
From: Bo Persson on 3 Mar 2010 11:34
Michael Goldshteyn wrote:
> "Mycroft Holmes" <psion.s5(a)gmail.com> wrote in message
> news:9812cb54-c21d-4f44-b581-9e17df8a0052(a)15g2000yqa.googlegroups.com...
>> Hi all,
>>
>> we have a large template-based set of headers; they are pretty much
>> standard compliant and we cross-compile with VS2005, VS2008, the
>> intel compiler and some versions of gcc. A few days ago we tested
>> VS2010 RC and we found the following problems: ...
>
> Wow! MS is refusing to fix this bug, saying it does not meet their
> "triage bar." I would strongly recommend that anyone who uses the
> Visual C++ compiler go to the following link and up-vote this bug
> so that it gets fixed before VS 2010 RTM is released:

I don't think you can get anything less than a super MEGA-bug fixed
between an RC and an RTM. Something like formatting the harddisk or
accidentally installing Linux.

In your case, I believe there is a workaround in using a pointer to
function in place of the function itself. Hardly worth stopping the
release while waiting for the real fix.


Bo Persson


From: Stephan T. Lavavej [MSFT] on 3 Mar 2010 19:04
Correct: a bug has to be setting kittens on fire *twice* in order for it to
be fixed between RC and RTM.

I've fixed exactly 1 bug in the STL between RC and RTM. (Those poor
kittens.) In the compiler front-end, where small changes can have drastic
effects, no bugs have been fixed between RC and RTM, and we're pretty sure
that's true for the compiler back-end and the linker as well. (I'd have to
ask about MFC and our other libraries.)

While you may disagree with an individual triage decision, you can surely
agree that last-minute fixes are potentially destabilizing. You don't want
us performing brain surgery right before shipping something that you'll have
to live with for years.

The best way to get bugs you care about fixed, helping yourself and helping
us, is to test betas as early and as thoroughly as possible. In each
successive beta period we can make fewer and fewer fixes (using VC10 as an
example: VC9 SP1 to VC10 CTP, CTP to Beta 1, Beta 1 to Beta 2, Beta 2 to RC,
RC to RTM), so the earlier you report bugs, the better.

We try to fix all of our bugs before shipping - that's what devs and testers
get paid to do, after all - but some will inevitably slip through. Only
you, by compiling and running your own code, can find out which bugs will
affect you. By reporting them, you're ensuring that we become aware of
common bugs earlier than we otherwise would have (for bugs that our devs,
our testers, or other customers would have run into later), and that we
become aware of obscure bugs affecting you when we otherwise wouldn't have
known about them.

Stephan T. Lavavej
Visual C++ Libraries Developer

"Bo Persson" <bop(a)gmb.dk> wrote in message
news:7v7hdaF1ebU1(a)mid.individual.net...
> Michael Goldshteyn wrote:
>> "Mycroft Holmes" <psion.s5(a)gmail.com> wrote in message
>> news:9812cb54-c21d-4f44-b581-9e17df8a0052(a)15g2000yqa.googlegroups.com...
>>> Hi all,
>>>
>>> we have a large template-based set of headers; they are pretty much
>>> standard compliant and we cross-compile with VS2005, VS2008, the
>>> intel compiler and some versions of gcc. A few days ago we tested
>>> VS2010 RC and we found the following problems: ...
>>
>> Wow! MS is refusing to fix this bug, saying it does not meet their
>> "triage bar." I would strongly recommend that anyone who uses the
>> Visual C++ compiler go to the following link and up-vote this bug
>> so that it gets fixed before VS 2010 RTM is released:
>
> I don't think you can get anything less than a super MEGA-bug fixed
> between an RC and an RTM. Something like formatting the harddisk or
> accidentally installing Linux.
>
> In your case, I believe there is a workaround in using a pointer to
> function in place of the function itself. Hardly worth stopping the
> release while waiting for the real fix.
>
>
> Bo Persson
>
>

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Endianness of padded scalar objects - Correction
Next: Click in the command prompt window pauses the application