Date: Wed, 9 Jan 2019 16:04:32 -0700 From: Rebecca Cran <rebecca@bluestop.org> To: Gavin Howard <gavin.d.howard@gmail.com>, Devin Teske <dteske@freebsd.org> Cc: Devin Teske <dteske@freebsd.org>, "=?utf-8?Q?freebsd-arch=40freebsd.org?=" <freebsd-arch@freebsd.org> Subject: Re: GNU-compatible, BSD-licensed bc Message-ID: <etPan.5c367ea2.327b23c6.2866@bluestop.org> In-Reply-To: <54ECF149-5ACD-4568-ADF5-FB4736B35DA1@FreeBSD.org> References: <54ECF149-5ACD-4568-ADF5-FB4736B35DA1@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On January 9, 2019 at 4:02:57 PM, Devin Teske (dteske@freebsd.org(mailto:dteske@freebsd.org)) wrote: > > Yes. -Weverything is the strictest I have ever seen. > > Often times I find that software cannot be compiled with -Weverything despite > passing -Wall -Wextra because some of the system/library headers fail checks. > > I've often considered a great accomplishment when I can pass -Weverything. From https://embeddedartistry.com/blog/2017/3/7/clang-weverything : “Clang helpfully provides a flag called -Weverything. Unlike -Wall, the -Weverything flag really will enable all warnings. This flag is especially useful if you are a warning lover - new warnings will automatically be enabled when you upgrade clang/Xcode. Turning -Weverything can be an eye-opening experience, even for those who religiously squash warnings. I often turn on -Weverything temporarily to review any of the less-common warnings and see what's worth fixing in my code base.”
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?etPan.5c367ea2.327b23c6.2866>