On Fri, 13 Jun 2008, Benjamin Kirk wrote: > Any better suggestion than renaming the libmesh one? Perhaps > trilinos_epetra_vector.h or something like that? If we prepend trilinos_* I > think it will be easier to navigate in the long run... Otherwise we need to > remember ml_*, aztec_*, nox_*, ... and whatever else all belong to the > trilinos interface.
I'd prefer libmesh_epetra_vector.h personally; it sounds more misleading than trilinos_, but that way we can be certain there won't be any namespace clashes. Or, for a more radical but perhaps more correct suggestion: The C equivalent of "namespaces" for headers is directories. If we redo our compiler flags so that just a top-level libMesh include directory is searched, then we could include libMesh headers with lines like: #include "libmesh/mesh/mesh.h" and it simply wouldn't matter if some third-party software decided that "mesh.h" was a good name for one of their own headers. This is an API-breaking sort of change, but we've accumulated a number of those lately. I recently helped Vikram move some old code up to libMesh SVN, and it turns out that Mesh to MeshBase, assert to libmesh_assert, CFLAGS to libmesh_CFLAGS, etc all add up when you have to make those changes all at once. libMesh 0.6.9 is already going to need some serious release notes attached. --- Roy ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
