[petsc-dev] C++11, compatibility versus simplicity

Jed Brown jedbrown at mcs.anl.gov
Thu Oct 3 11:04:06 CDT 2013


Karl Rupp <rupp at mcs.anl.gov> writes:
>> This means that to be safe, all libraries in the stack should be
>> compiled with -std=c++11.  So despite the source compatibility issues, I
>> think we have to make C++11 a global choice and complain to third
>> parties if they can't build with it.
>
> Although painful, this seems to be the only reasonable path to go.

So should we (a) turn it on by default for all compilers that support it
and give an option to use an earlier standard, (b) turn it on
automatically as a side-effect of enabling a package that requires it,
or (c) require that the user configure --with-cxx-dialect=C++11?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131003/74f59249/attachment.sig>


More information about the petsc-dev mailing list