This is the mail archive of the
mailing list for the Cygwin project.
Re: Updated [test]: coreutils-8.24-2
- From: Sam Edge <cygwin at dwalin dot fsnet dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Thu, 27 Aug 2015 23:57:53 +0100
- Subject: Re: Updated [test]: coreutils-8.24-2
- Authentication-results: sourceware.org; auth=none
- References: <001c01d0e04c$d8ebc210$8ac34630$ at bonhard dot uklinux dot net> <000001d0e051$965f38a0$c31da9e0$ at bonhard dot uklinux dot net> <55DE4B8B dot 6000401 at redhat dot com> <55DF6961 dot 9040804 at dwalin dot fsnet dot co dot uk> <55DF7265 dot 8050607 at lysator dot liu dot se> <op dot x31nexczofd6j1 at nebbiolo dot upc dot de>
- Reply-to: cygwin at cygwin dot com
On 27/08/2015 21:33, Helmut Karlowski wrote:
> Did you mean: "The compiler-warning would inform you that the value is
> not set in a code-path"?
I'd agree if I was always in the position of starting projects from
scratch. All compiler warnings should be errors and disabling a compiler
warning has to have a valid justification during review, yes.
But try it with an existing code base. That's when you need
deterministic behaviour from your modifications with minimal disturbance
to anything else.
> That's why I usually try to avoid initializing auto-variables (and
> maybe save some bytes).
If you can afford the tech debt recovery time to change your compiler
warnings to errors or sift through the build output - and prove to your
QA/RA that you don't have to re-certify the product.
But you're unlikely to save any bytes using a modern compiler.
Anyway, we're off-topic so adieu.
-- Sam Edge
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple