> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of John > Peterson > > On Mon, Nov 22, 2010 at 3:09 PM, Chetan Jhurani > <[email protected]> wrote: > >> -----Original Message----- > >> From: John Peterson [mailto:[email protected]] > >> > >> #2a - I agree that macros are evil, but this one is pretty benign: > >> > >> #define DISALLOW_COPY_AND_ASSIGN(TypeName) \ > >> TypeName(const TypeName&); \ > >> void operator=(const TypeName&); > > > > > > Just a curious lurker here. What about a non-macro solution: > > > > http://www.boost.org/doc/libs/1_43_0/boost/noncopyable.hpp > > This is a nice solution but IMHO changing the inheritance hierarchy is > a little intrusive just to get two little functions disabled!
Makes good sense. I was thinking in terms of changing a few classes only and not the whole codebase. Chetan > > -- > John ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
