Re: Please read this: Is there a bug in std::unique_ptr? (Repost, the code in old post is wrong)

From:

Jayden Shui <jayden.shui@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Fri, 16 Dec 2011 08:20:59 -0800 (PST)

Message-ID:

<28d992a0-ae10-4f47-9997-bf28b726cfb0@x7g2000yqb.googlegroups.com>

On Dec 16, 10:45 am, "Alf P. Steinbach" <alf.p.steinbach
+use...@gmail.com> wrote:

On 16.12.2011 15:54, Jayden Shui wrote:

Hi All,

I accidently find that the following code works with Visual C++
compilation

#include<memory>
#include<iostream>
using namespace std;

int main()
{
unique_ptr<int> const p(new int(1));
unique_ptr<int>& q = p; // assign a constant to a non-cons=

tant

reference
    q.reset(new int(2));
    cout<< *p; // output 2
    return 0;
}

My question is from the 2nd statement of assigning a constant to a non-
constant reference. I think the compiler should report an compilation
error, but it doesn't. Is there a bug in the code of unique_ptr in the
std template library?

What did you fail to understand about my answer?

It does not compile with Visual C++ 10.0, and it does not compile with
MinGW g++ 4.4.1.

Show your compilation that works, stop spamming/trolling.

Sorry for disturbing. I found the problem. I am in fact using intel c+
+ in visual studio. Intel c++ compiler passes it by treating it as
only a warning.