[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C++11 now default?
From: |
Mike Miller |
Subject: |
Re: C++11 now default? |
Date: |
Mon, 22 Feb 2016 12:07:42 -0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
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 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.
--
mike
- Re: C++11 now default?, Rik, 2016/02/22
- Re: C++11 now default?,
Mike Miller <=
- Re: C++11 now default?, John W. Eaton, 2016/02/22
- Re: C++11 now default?, Mike Miller, 2016/02/22
- Re: C++11 now default?, John W. Eaton, 2016/02/22
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, John W. Eaton, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Mike Miller, 2016/02/23
- Re: C++11 now default?, Ben Abbott, 2016/02/23