On Jun 21, 2010, at 3:29 PM, Roy Stogner wrote: > > On Mon, 21 Jun 2010, Derek Gaston wrote: > >> I'm not sold on either direction... but I do enjoy not having to >> deal with a libmesh namespace now. But laziness doesn't justify >> anything. > > How about we decide not to decide? > > "using namespace libMesh;" in libmesh_common.h, wrapped in > something like > #ifndef LIBMESH_USE_NAMESPACE > which gets defined by something like > ./configure --disable-separate-namespace
If this works then users (like myself) who like not needing to use libmesh:: can put "using namespace libMesh" in our own header files that get included. I have one root header file for my library (much like libmesh_common.h) where I can put this and all of my code will be fine (as will my user's code). That's not an objection to your suggestion... that sounds fine to me too. But if the fix is that trivial... it might not require it. Derek ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
