Absolutely 100% against C++11
Portability is one of the main areas where we are well beyond our
competition. I would say that nearly half of the cluster installations we
do are using compilers that are at least 4 to 5 years old. We can't afford
to tell everyone "you need to upgrade your compiler" as many of these
people are locked into some ancient Redhat and changing that is nontrivial.
C++11 is not going going to be viable for a few more years. I wish it were
not the the case... we talk about how we would love to use some of those
features all the time. But... it just can't happen yet.
Everything else sounds good to me. It will force me to get off my butt and
finally stop using comm_world ;-)
Also, another suggestion: MOOSE is going open source soon (really!) and
it's going up on GitHub as well. Is now the time to start looking into the
development model/process for libMesh (and MOOSE). ie codifying a set of
branches (like devel/stable/master) and putting together a plan for testing
everything, etc?
We talked about this a while ago and we all decided to wait and see how
things were working on GitHub before making any decisions... and I think
that time might be upon us.
Derek
On Mon, Jan 13, 2014 at 8:50 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> OK, this could kick off a lot of discussion, but here goes…
>
> I'd like to polish a release this week if possible. Roy'd previously
> mentioned calling it 1.0, but I'd like to go with v0.9.3 because
> 1) I'm not aware of anything drastically different vs 0.9.2, but correct
> me if I'm wrong;
> 2) In any case I'd like to wire brush the code and remove all the APIs
> that have been deprecated for ages;
> 3) I'd like to remove the default comm_world business for 1.0.
>
> So v0.9.3 could be imminent with then 1.0 a API cleanup follow-on.
>
> But what about C++11? I could see 1.0 as a 'maintenance stream' where we
> back port important bug fixes but otherwise leave it alone. New
> development could occur on a master requiring C++11, unless there is a
> consensus otherwise. It's 2014 already, and a good quorum of C++11
> features are implemented in pretty much all relevant compilers.
>
> Specifically for the MOOSE guys, what's the oldest compiler you are
> compelled to support?
>
> -Ben
>
>
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Libmesh-devel mailing list
> Libmesh-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
