On Thu, Sep 13, 2012 at 9:06 AM, Kirk, Benjamin (JSC-EG311) <benjamin.kir...@nasa.gov> wrote: > OK, there might be some resistance to this, but... > > I've been thinking about putting a little include file header safety into > libMesh. Basically, right now all our header files have to have unique > names because their directories get added to the include path. Further, none > of these can have the same names as any header files in user code. > > This could easily be fixed by not specifying the the include/... > subdirectories to the compiler, so > > #include "dof_map.h" > > becomes > > #include "base/dof_map.h" > > or maybe even better > > #include "libmesh/base/dof_map.h"
Better because more unique? Feels a little "boost"y to me, but I guess I could get used to it. > We could even keep the old functionality through a configure option, which > we set to suppress adding the extra paths. On trunk we set this option to > suppress the extra paths but could turn it on for a release or two... Hmm... I wouldn't mind just going cold turkey on switching this over. I don't think people will start switching over their apps in the meantime, as long as the default configure option maintains the status-quo. -- John ------------------------------------------------------------------------------ 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
