On Thu, 13 Sep 2012, Kirk, Benjamin (JSC-EG311) wrote: > OK, there might be some resistance to this, but...
>From a software reusability standpoint, it was a lousy mistake not to put our headers into the closest thing C/C++ has to a "namespace", and we should have fixed it around the same time we were wrapping all our global names into a real namespace. We definitely want either #include "libmesh/dof_map.h" or #include "libmesh/base/dof_map.h" in the long run. But from a backwards compatibility standpoint, I always thought it would be too tricky to juggle this around without immediately horribly breaking everyone's code. However, if you can work out a configure option such that old-style and new-style include statements both work for a release or two (the same way we're in the middle of doing things with the namespace libMesh) then I'd love to see this change. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
