On Jun 21, 2010, at 4:35 PM, Roy Stogner wrote: > No way. With "libMesh::Mesh" we can use the namespace features and > probably get away with a few lines of code in every file (deep breath > in, Derek, deep breath out...); with "libMesh_Mesh" there really > wouldn't be a way to avoid a 20K line patch.
Honestly, I'm not that worried about Mesh. In fact, if you just want to stick that guy into the libMesh namespace and leave everything else alone... that's fine with me. I'm more worried about things like TypeVector. Think about code that could look like this: std::vector<std::vector<libMesh::TypeVector> > > triple_vec; ... libMesh::TypeVector temp = triple_vec[0][1]; Well... now that I write it out it doesn't look too horrible.... hmmm. In fact, it kind of looks like the "right thing" to do. Double hmmmm. I'll leave it up to you guys. I might still stick "using namespace libMesh" in one of my main header files though. Mostly to shield my users from needing lbMesh:: all over the place (or "using"). But you guys should do what's right for the library. 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
