Message-ID: <5421FF2E.4010709@sbcglobal.net>
Date: Tue, 23 Sep 2014 16:15:58 -0700
From: Girvin Herr <girvin DOT herr AT sbcglobal DOT net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20131204 Thunderbird/17.0.11
MIME-Version: 1.0
To: geda-user AT delorie DOT com
CC: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] Banging my head against the guile-for-windows wall
References: <20140923045453 DOT 56dc3de2 AT akka> <CAOuGh8_bfL2KJDLt-qkU7v0wS3UBkbHeej6ScVLJJfHnOR_6oQ AT mail DOT gmail DOT com> <lvssr7$lun$1 AT ger DOT gmane DOT org>
In-Reply-To: <lvssr7$lun$1@ger.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com


On 09/23/2014 03:39 PM, Kai-Martin Knaak wrote:
> Bob Paddock wrote:
>
>> Warnings *are* errors, they should not be ignored.
>>
>> I have found it rare for most GCC based code to compile with
>> anything less than -std=gnu99.
>>
>> Rather than disable Werror, remove the -ansi and possibly the
>> -pedantic, add -std=gnu99.
>>
> Fair enough.
> To see this amount of warnings in code that is supposed to be the part
> of the backbone of the GNU suite is a bit disconnecting, though. This
> interpreter was started by gnu-gurus twenty years ago. I'd expect them
> to have ironed out this kind of wrinkles long time ago. But who am I
> to judge? After all, I wouldn't complain about warnings at all, if the
> result would just run...
>
> ---<)kaimartin(>---
>
>
I have a software and hardware background and I treat warnings the same 
as errors.  The compiler generates a warning when it can't decide if the 
programmer really wanted it coded that way or they are real errors.  
Therefor, warnings are red flags to programmers to look real hard at the 
code to confirm that it will, indeed, run fine with that warned code, or 
is it a real error that needs fixing.  So, your experience with code 
that has compilation warnings could be that the programmer has decided 
those warnings were okay.  In my case, my released code has no warnings 
- period.  If I get a warning but I decide the code should work 
properly, I change the code to satisfy the compiler, not let it go.  
Yes, I have seen released code that still has warnings, but I cringe 
when I see it and am very reluctant to run it on my computer because it 
reflects on the programmer's quality.  If there are warnings, what 
other, worse bugs are in there?  Sometimes I have no choice but to 
accept it, especially if I have no time to dig into the code to fix it.
Girvin Herr