Anders Logg wrote: > There seems to be a problem (among many) with the current design of > the Function classes (see thread "evaluating higher order mesh function"). > > In particular, the finite element is missing in DiscreteFunction. My > suggestion would be to just add it and let a DiscreteFunction consist > of the following four items which are always available: > > mesh, x, dof_map, finite_element >
Sounds fine. I thought that a DiscreteFunction already had a FiniteElement. Should a DiscreteFunction own its FiniteElement? Could FFC or whatever/whoever generates the ufc::finite_element somehow provide a unique identifier for that element type? I don't particularly like the precompiled elements, and an identifier would help on this front. Garth > Is this enough, and what other issues to we need to fix? > > > > ------------------------------------------------------------------------ > > _______________________________________________ > DOLFIN-dev mailing list > [email protected] > http://www.fenics.org/mailman/listinfo/dolfin-dev _______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
