Ah yes. Then my only objection is if we use it somewhere for filling data in UFC structs. But perhaps in that case it can be replaced by a new member function that does just that (fills in the UFC vertex data) so that function can be implemented differently for different representations.
-- Anders mån 15 juni 2015 kl 20:56 skrev Garth N. Wells <[email protected]>: > On 15 June 2015 at 19:47, Anders Logg <[email protected]> wrote: > > MeshGeometry::x(std::size_t n) means give me the x-coordinate for vertex > n. > > Nope, the full signature is > > double* MeshGeometry::x(std::size_t n); > > so it gives a pointer to the coordinate values of vertex n. > > Garth > > > > Shouldn't that still be supported, irrespective of implementation > details? > > > > -- > > Anders > > > > mån 15 juni 2015 kl 18:34 skrev Chris Richardson <[email protected]>: > >> > >> > >> 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 > > > > > > _______________________________________________ > > fenics mailing list > > [email protected] > > http://fenicsproject.org/mailman/listinfo/fenics > > > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics >
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
