> #include "libmesh/base/dof_map.h" > in the long run. That's easy enough.
the plan would be to make $LIBMESH_ROOT/include/libmesh and move our current $LIBMESH_ROOT/include/* there. > 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. Should be really easy to do. By default I'll have -I$LIBMESH_ROOT/include only, which will require full path specification in include statements. But configure can add -I$LIBMESH_ROOT/include/libmesh/base ... for backwards compatibility as needed. Obviously this won't allow us to have foo.h in multiple directories until we totally eliminate the backwards compatibility, but that's OK... -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
