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

[Matthew Knepley]

On Thu, Oct 3, 2013 at 11:04 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> 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?
>

I think c). It just another package thing to require. I think this is a
fairly bad decision
for Elemental considering the restriction it will have on the user base.
Trilinos-esque.

  Matt

-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131003/94a79d3e/attachment.html>