From owner-freebsd-current Thu Jan 28 00:47:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09480 for freebsd-current-outgoing; Thu, 28 Jan 1999 00:47:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09474 for ; Thu, 28 Jan 1999 00:47:24 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id DAA29006; Thu, 28 Jan 1999 03:47:27 -0500 (EST) Date: Thu, 28 Jan 1999 03:47:27 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: Nate Williams , Archie Cobbs , Garrett Wollman , current@FreeBSD.ORG Subject: Re: btokup() macro in sys/malloc.h In-Reply-To: <199901280603.WAA93627@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 Jan 1999, Matthew Dillon wrote: > > :> then we need to update sytle(9) to reflect that. > :> > :> In fact, style(9) should say: > :> > :> If at all possible, your code should compile without warnings > :> when the gcc -Wall flag is given. > : > :I disagree. As has been shown many times in the past (and I suspect the > :down-under constituent will show that at least a couple of the > :'warnings' fixes will be wrong and hide bogus code), making -Wall a goal > :causes people to cover up bad code with bad casts and such. > : > :'-Wall' is *NOT* a good design goal. > > Nonsense. -Wall does *NOT* contribute to a bad programmer programming > badly, and I found at least three fairly serious mistakes when I turned > it on. > > I mean, come on... by your argument the compiler might as well give up > and not bother warning you about anything! And for the exact antithesis of silence, TenDRA has the most wonderful warnings, and it's a great free linter (but does its job better than standard lint), while producing as good code as GCC most of the time. That takes not into account once when I ran into some glaring bugs in the compilation, but at least the warnings were correct :) > > -Matt > Matthew Dillon > > > :Nate > : > :To Unsubscribe: send mail to majordomo@FreeBSD.org > :with "unsubscribe freebsd-current" in the body of the message > : > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message