A couple of words about --enable-strict. It currently just adds -ansi -pedantic -Wno-long-long, but
Should check for strict ANSI C, so you can make sure no one is using GNU extensions.
For --enable-strict, I'd instead add a -Werror, and possibly make that the default.
Warnings depend what compiler and processor you are compiling on - I think that would break many builds that would have succeeded otherwise but that you cannot test.
This would force developers to fix the warnings immediately.
Not really. Trying to force people to do things by devious mechanical means is usually counter-productive. The sort of people who see warnings but do not care to fix them will just turn all error checking off. M _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
