On Mon, Jun 21, 2010 at 4:29 PM, Roy Stogner <royst...@ices.utexas.edu> 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?
Then, according to the awesome band known as Rush, "you still have made a choice" ;-) > "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 Would it really be that simple? That doesn't put things like our Mesh into a libMesh namespace. It just pulls the libMesh namespace into the existing compilation unit, that namespace will be empty (except for the few things we have in it now.) Perhaps I misunderstood, but I don't think we can configure on/off namespacing the entire library in a couple lines... -- John ------------------------------------------------------------------------------ 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
