The first constructor for FiniteElement seems to be wrong. When we use shared pointers, I thought the conclusion was to have two constructors: one that takes a reference and one that takes a shared_ptr. This is what we do in NewFunction using NoDeleter.
In the first case, the user owns the data and in the second case the user and the created object share the data. I'm having trouble now when initializing a dolfin::FiniteElement from a ufc::finite_element in Python since both Python and the created dolfin::FiniteElement want to delete the ufc::finite_element. -- Anders
signature.asc
Description: Digital signature
_______________________________________________ DOLFIN-dev mailing list [email protected] http://www.fenics.org/mailman/listinfo/dolfin-dev
