On Jun 21, 2010, at 11:49 AM, John Peterson wrote: > In source files yes, but if they've written their own headers (as you > mention below) I think the general rule of thumb is you don't put > "using" declarations there. So, the more extensive the user project, > the more extensive the change will be...hopefully Derek will chime in > about how much the proposed change would affect his work.
Well... on the one hand I agree that it might be the right thing to do. On the other hand libMesh is just TOO pervasive in it's users codes. What I mean by that is that just about every line would either have to have a libmesh:: somewhere in it... or every file would have to have "using" in it. I'm not against it... but we do have on the order of hundreds of .C files (not to mention all of OUR users would also have to put this in all of their implementation files). 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. I guess my initial vote will be to wait for Petsc to implement a namespace for Sieve and then reevaluate. 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
