The MeshFunction class has a lot of constructors. This roughly doubled recently with the switch to using shared pointers for the mesh (now ~10 constructors).
What are the opinions on having duplicate reference/shared_ptr constructors in MeshFunction? Should we just have shared_ptr versions? This only affects the C++ interface. The Python interface uses the shared_ptr version (but does requires the other constructors being marked in the SWIG layer as to be ignored, which is easy to forget). Garth _______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
