Re: Will version 4.2 require C++11?

[Mike Miller]

On Fri, May 20, 2016 at 16:29:22 -0700, Rik wrote:
> The thing with 'auto' is that it is quite a binary decision.  Prior to
> C++11 the auto keyword meant automatic variable, i.e, an ordinary local
> variable that was not stored in a register as specified by the 'register'
> keyword.  If we are using it even once in its new sense, then we require
> C++11 conformance.  We should test for that in configure, and then we might
> as well use the rest of the C++11 features.  "In for a penny, in for a pound".

Right, we already do test for C++11 features in configure and
automatically add the -std options needed, so maybe we should introduce
an error if the basic feature set tested for there doesn't pass (via the
variable $ac_cv_prog_cxx_cxx11).

My understanding is that gcc 4.8 will continue to build Octave, but
earlier versions may not. That seems reasonable to me (someone who not
that long ago regularly built Octave with gcc 4.1).

-- 
mike