Date: Sun, 16 Feb 2014 09:04:37 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Bruce Evans <brde@optusnet.com.au> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Dimitry Andric <dim@FreeBSD.org> Subject: Re: svn commit: r261916 - head/sys/dev/xen/console Message-ID: <9AECF0D9-9230-4312-858D-E0C92674FC18@FreeBSD.org> In-Reply-To: <20140216134006.R788@besplex.bde.org> References: <201402151237.s1FCbRnh000507@svn.freebsd.org> <20140216035823.I2978@besplex.bde.org> <8C22DE47-60F2-47C0-938D-590324818872@FreeBSD.org> <20140216134006.R788@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Feb 2014, at 04:09, Bruce Evans <brde@optusnet.com.au> wrote: > [a long list of corner cases where the warning may not be correct] Fortunately, the goal of compiler warnings is not to address every = possible case, but rather to minimise false positives while still giving = useful results. The warning can be turned off if you are using the C = preprocessor in a way designed to provide cautionary tales to young = programmers, but for everyone else it makes sense to have it on by = default. Anyone using a single file as both the main file for a compilation unit = and as an included file in others, deserves to have a new antipattern = named after them so that their name can live in infamy, but should not = in any way be allowed to influence the design of compiler warnings. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9AECF0D9-9230-4312-858D-E0C92674FC18>