On Wed, Feb 05, 2014 at 11:32:07AM +0100, Martin Sandve Alnæs wrote:
> On 4 February 2014 22:30, Anders Logg <[email protected]> wrote:
>
>     The initial testing of C++11 features in DOLFIN seems to have gone
>     relatively smooth. All buildbots are green and the few reports we have
>     had on build problems seem to have been resolved.
>
>     I would therefore suggest that we:
>
>     1. Allow full use of C++11 features in DOLFIN, with the exception of
>     features that are not well supported by the majority of relevant
>     compilers
>
>
> That's hardly full use. We should define what to use,
> for example only features supported by gcc 4.4:
> http://gcc.gnu.org/projects/cxx0x.html

Sounds good. I don't suggest that we start using everything from
C++11, just to allow useful and supported features. Each addition
needs to be introduced and tested carefully.

>     - we'll have to figure out which those features are by trial
>     and error. Examples of good features are std::shared_ptr, std::tuple,
>     auto.
>
>
>
>
>
>     2. Replace all boost::shared_ptr by std::shared_ptr in DOLFIN.
>
>     3. Change the build system for UFC to distutils.
>
>     4. Merge UFC into FFC.
>
>     4.5. Figure out how we handle version numbers from UFC from now on.
>          Can we make a restart from 1.4?
>
>
> When UFC is merged into FFC we won't make UFC releases anymore,
> so it will be "UFC from FFC 1.4" or something like that.
>
>
>
>     5. Release FEniCS 1.4.
>
>     Comments, objections?
>
>
> In a hurry? I haven't even had the time to build with c++11 yet.
> I'd like to get the multidomain infrastructure merged before 1.4.

I don't think we should wait for particular features before we make a
release. Releases should happen often whenever something important has
changed. There will be plenty of time to merge multidomains into 1.5,
1.6 etc.

I'm not in a particular hurry to get this C++11 into 1.4, but I would
like to make a quick release to set the pace for new and frequent
releases.

--
Anders
_______________________________________________
fenics mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics

Reply via email to