>>> I haven't complained, but I've already hit several cases where I had to >>> rename >>> my own header file because it collided with a libMesh header name. This >>> would >>> fix any further possibilities of this happening. >> >> Likewise. For example, we have 'utility.h' just hanging out there, thereby >> precluding users from having the same. Really? >> >> So it's more than the classes, which was your reply... >> >> and it's not just for the users, but when some poorly constructed project we >> decide to interface with also has a utility.h - what then? > > How 'bout we rename all our headers from foo.h to libmesh_foo.h? > > Hmm... originally I was going to post this as a joke, but maybe it's > simpler than messing with configure/make stuff?
Well, if you guys have such a vested interest in insulating Moose users from our churn, why make them responsible for knowing our header names at all? You could create your own libmesh.h which includes all our headers - hell, and then even create a precompiled header out of it! -Ben ------------------------------------------------------------------------------ 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
