[Dune] [#989] Use C++11 instead of C++0X

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#989 - Use C++11 instead of C++0X
User who did this - Jö Fahlke (joe)

----------
As far as I remeber, Dune's C++0x check does two things:

 1. It tries to force $CXX into C++0x mode by appending options like -std=c++0x
 2. If it succeeds, or if the compiler was in C++0x mode to begin with, it sets a compiler define that announces C++0x capability.

If there are compilers out there for which -std=c++0x is not enough to get them into C++11 mode, then we definitely should add the correct option for them to the list of options tried in step 1.  However, this is really not of a high urgency since the user can always say "CONFIGURE_OPTS="CXX='c++ -my-weird-option'", if he really needs a C++11-compiler.

Otherwise I really don't see a reason to go do a global s/c++0x/c++11/g in the whole of dune.  It's nicer, of course, but on the other hand it will probably require some transition code, and that is ugly.  And ultimately, it will become irrelevant because eventually we will drop support for compilers that don't operate in C++11-mode per default anyway.
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=989#comment2941

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.