Date: Wed, 20 Jan 1999 19:23:03 -0600 (CST) From: Henry Miller <hank@black-hole.com> To: Peter Wemm <peter@netplex.com.au> Cc: Bill Fenner <fenner@parc.xerox.com>, Bruce Evans <bde@zeta.org.au>, cvs-committers@FreeBSD.ORG Subject: Re: -Werror Message-ID: <Pine.BSF.3.96.990120192004.57719B-100000@daphne.bogus> In-Reply-To: <199901201228.UAA19912@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 20 Jan 1999, Peter Wemm wrote:
> Bill Fenner wrote:
> > Or should simply be caught by --don't-be-lazy . -Werror doesn't help
> > when the committer thinks that it's so obvious and simple that there's
> > no need to even try building it.
>
> The last time the warnings, etc, thing came up, the consensis was:
>
> In development mode, all practical warnings turned on.
> In release mode, turn them off. It's no use scaring the users about
> something they have little or no control over.
>
> Personally, I'd be quite happy to have -Werror turned on during
> development, providing that it doesn't make it into any releases.
Might I suggest a possibal compromise: a couple weeks before a release
turrning on -werror to force the issue (we want release code to be clean)
with devolpers. In between just -Wall is probably good enough to note
possibal problems, those who have a real bug will probably place those
higher then unrelated warnings.
I think it is a good idea to have clean release code, but what happens
inbetween will always be less nice.
--
http://www.black-hole.com/users/henrymiller/
hank@black-hole.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990120192004.57719B-100000>