This warning in the extract test case should also be disabled for Intel 8: ..\libs\python\test\extract.cpp(59): warning #473: returning reference to local temporary return extract<std::string const&>(x); ^ BTW, is this a compiler defect? S.
Stefan Slapeta <stefan_nospam_@slapeta.com> writes:
This warning in the extract test case should also be disabled for Intel 8:
..\libs\python\test\extract.cpp(59): warning #473: returning reference to local temporary return extract<std::string const&>(x); ^
Feel free.
BTW, is this a compiler defect?
Yes. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of David Abrahams
This warning in the extract test case should also be disabled for Intel 8:
..\libs\python\test\extract.cpp(59): warning #473: returning reference to local temporary return extract<std::string const&>(x); ^
Feel free.
Should be done by somebody with a write access. Just increase the Intel version number in the code from 7 to 8.
BTW, is this a compiler defect?
Yes.
I still don't see why? Aren't you (indirectly) returning a reference to a local object? std::string const& extract_string_cref(object x) { // [disable warnings] return extract<std::string const&>(x); // [enable warnings] } Stefan
"Stefan Slapeta" <stefan@slapeta.com> writes:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of David Abrahams
This warning in the extract test case should also be disabled for Intel 8:
..\libs\python\test\extract.cpp(59): warning #473: returning reference to local temporary return extract<std::string const&>(x); ^
Feel free.
Should be done by somebody with a write access. Just increase the Intel version number in the code from 7 to 8.
Done.
BTW, is this a compiler defect?
Yes.
I still don't see why? Aren't you (indirectly) returning a reference to a local object?
std::string const& extract_string_cref(object x) { // [disable warnings] return extract<std::string const&>(x); // [enable warnings] }
No. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Stefan Slapeta <stefan_nospam_@slapeta.com> writes:
David Abrahams wrote:
"Stefan Slapeta" <stefan@slapeta.com> writes:
I still don't see why? Aren't you (indirectly) returning a reference to a local object?
No.
Thanks. This answer will make it much easier to submit a DR.
Don't waste your time; I've already done it. Intel will never accept it because of its goal of "bug-compatibility" with VC++. :( -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Stefan Slapeta <stefan_nospam_@slapeta.com> writes:
David Abrahams wrote:
Don't waste your time; I've already done it. Intel will never accept it because of its goal of "bug-compatibility" with VC++.
If you haven't done so already, you should submit it to Microsoft for VC 8.
It's not present in Vc8. This is an Intel and VC7.1 problem. And I am on vacation :) -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Stefan Slapeta writes:
Doug Gregor wrote:
I'm going to cut off your access to Boost if you don't start vacationing soon :)
Believe me, there are some others who can't sleep well during their vacation because they want to observe the progress of the upcoming boost release :)
And their contributions towards the goal are very much appreciated! -- Aleksey Gurtovoy MetaCommunications Engineering
participants (5)
-
Aleksey Gurtovoy -
David Abrahams -
Doug Gregor -
Stefan Slapeta -
Stefan Slapeta