[Octave-patch-tracker] [patch #8906] configure check support for c11 and c++11

[John W. Eaton]

Follow-up Comment #2, patch #8906 (project octave):

To the statement "it's ok to use as long as it's not a requirement", I'd like
to add that it is not OK to use C++11 for basic functionality that could be
implemented without C++11 features.  So the change I proposed for acos is OK
because it allows acos to work even if C11 and C++11 features are not
available.  But that means more work for us now because to use the shiny new
C++11 feature, we still need to provide a fallback method.

On the brighter side, I think we may be close to being able to just use at
least some C++11 features without requiring fallback methods if they are
supported by reasonably recent versions of GCC and Clang.  With mxe-octave, we
have a way to build Octave with a current version of GCC when the system
compiler is not sufficient.

Perhaps after 4.2 (or will it be 5.0?) we could start using C++11 features and
if people want to build Octave with ten year old compilers, we can tell them
that they either upgrade their compiler (possibly using mxe-octave to do it)
or build an old version of Octave with their old compiler.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?8906>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/