|
From: | John W. Eaton |
Subject: | Re: C++11 now default? |
Date: | Mon, 22 Feb 2016 16:04:50 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 |
On 02/22/2016 03:07 PM, Mike Miller wrote:
On Mon, Feb 22, 2016 at 09:25:33 -0800, Rik wrote:We could always do as jwe suggested, albeit reluctantly, and introduce UNIQUE_PTR which uses a test in configure to determine whether std::unique_ptr or std::auto_ptr is available.FWIW, I'm able to build default with gcc 4.4 on CentOS 6, with the following caveats: * I have to explicitly declare CXX="g++ -std=gnu++0x", the automatic detection in configure doesn't work if the compiler doesn't fully support C++11. Without that option, the std::unique_ptr class is not found.
I'm beginning to think we should make the c++11 test optional using something like --enable-c++11 and have it disabled by default.
* I have to set the OCTAVE_DEPRECATED(msg) macro to be #define OCTAVE_DEPRECATED(msg) __attribute__ ((__deprecated__)) because apparently the optional msg argument was added in gcc 4.5.
That should be easy enough to fix with a configure check. jwe
[Prev in Thread] | Current Thread | [Next in Thread] |