On 8/10/11 12:16 PM, Roy Stogner wrote: > > On Wed, 10 Aug 2011, John Peterson wrote: > >> A problem I see with this (other than adding a lot of code just to >> silence the compiler) is that it won't be maintained by all (any?) of >> the developers. >> >> I for one do not plan to add extra warnings to compiler flags in opt >> mode, and don't recommend we do so by default either... > > No? I suppose that might not be fair to some users. But at the very > least I'd like to have some sort of --enable-all-warnings flag as part > of --enable-everything. So right off the bat I'd be keeping an eye on > opt-mode warnings every few weeks or so.
I personally think that it would be nice if at least the headers compiled cleanly. :-) Also, I would hope that it will be pretty easy to maintain at this point, although that is just a guess. Assuming this patch gets accepted, I will be building libMesh with extra warnings with METHOD=opt and can help with patches, although I certainly do not keep as up-to-date with the svn head as you folks. -- Boyce ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
