On Wed, 1 Jun 2011, Derek Gaston wrote: > Very cool.... do we need something like a > LIBMESH_INCLUDE_NO_WARN_BEGIN and LIBMESH_INCLUDE_NO_WARN_END that > could be set to compiler specific #pragmas at configure time?
That sounds like a pretty nice idea. Even after going so far as to edit my local MPI headers, I haven't gotten around to doing the same for (different problems in) the VTK headers... I'd worry a bit about disabling warnings this way, though. If you're instantiating a template or a macro that's defined in a header, for instance, and there's something wrong with your instantiation, does disabling warnings for the header also disable the warning about your own mistake? --- Roy ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
