http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53225
--- Comment #32 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-05 00:14:38 UTC --- (In reply to comment #30) > Sorry to be thick headed Jon. Perhaps you could boil it down to the essentials > here, are you saying that assignment is illegal in operator new so it is > proper > that there be no error and one gets the wrong result? Is that your point? > Answer me this, and I will drop the report. No, I'm saying you are not getting the wrong result. What you think is correct is not correct. I'm saying the behaviour you see is not a compiler bug, it's how C++ works. This bug report is *not* the right place to discuss it, take it to the gcc-help mailing list or *anywhere* else. "I don't understand C++" is not a valid bug. So I'm moving this to gcc-help and I'm closing the report again, if the description Please stop re-opening this report. I will discuss it elsewhere but not here. See http://gcc.gnu.org/ml/gcc-help/2012-05/msg00029.html for anyone who isn't sick of this yet.
