On 9/13/12 11:19 AM, "John Peterson" <peter...@cfdlab.ae.utexas.edu> wrote:
>> #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. better because I still want sudirectories to organize the header files. #include "libmesh/dof_map.h" would be fine but would require we create a libmesh directory inside each of our current subdirectories, and it is the only thing in there. So we'd have include/base/* -> include/base/libmesh/* include/enums/* -> include/enums/libmesh/* ... which seems a little strange at first thought but then again may be better - after all if we want to move a header between subdirectories why should a user care or have to update code? Hmm... I'm kinda reversing myself on that one... Thoughts?? >> 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. Yeah, I meant cold turkey on trunk but when we package up a distribution temporarily re-enabling the extra search paths. I'll get started on this. hardest part for me will be the script to fix all our existing stuff... regex'ing was never a strength! -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
