On Fri, 14 Sep 2012, Roy Stogner wrote:
> Plus, if you really want to push users into making their code more > random-third-party compatible right now, let's add a configure > option that turns on LIBMESH_REQUIRE_SEPARATE_NAMESPACE. At least > in that case there's been more than a little advance warning. Actually, I'm going to add that option myself, ASAP, defaulting it to the old ("using namespace libMesh" in libmesh_base.h) behavior. Enforcing separate namespaces manually is apparantly annoying enough that I haven't tested that case in too long, and I was just embarrassed to discover several little regressions in the support... --- Roy ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel