Anyone strongly opposed to switching on the compiler flag (-Werror) that says to treat all warnings as errors?
Apart from anything else, it seems quite a common cause of build problems is that newer compilers sometimes treat as errors things that were only warnings in older ones (as in a report on rg-user today). Also, I've just set up automated builds of the tree with a selection of configure options, and it's nice to be able to assume that anything reported on stderr is probably a problem. At the moment we have a few dozen warnings in the whole build. Most of them are unused parameters or local variables, or assignments between int and double or unsigned. While these are generally benign and not things I'd bother fixing without the -Werror flag to provoke me, I do think on the whole -Werror is good practice and I don't mind going through and dealing with them. But I want to know whether anyone else gives a crap about this first. If it bothers you I'll happily drop it. Chris ------------------------------------------------------- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
