Dear all,

I've been looking at:

https://bitbucket.org/fenics-project/fenics-developer-tools/wiki/Parameterized_geometries

today.

It seems like it might be a good idea to rewrite the interface to MeshGeometry in some way. If the geometry is going to be stored as xxxxxxyyyyyyzzzzzz etc instead of xyzxyzxyzxyz etc, or perhaps in some other unspecified way internally, then it makes sense to start deprecating methods such as MeshGeometry::x(std::size_t n), which rely on a specific internal data ordering - and to do it for this release... any opinions?

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

Reply via email to