Xref: utzoo gnu.gdb.bug:527 gnu.gcc.bug:2015 gnu.g++.bug:1523
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!jarthur!uci-ics!rfg
From: rfg@ics.uci.edu (Ronald Guilmette)
Newsgroups: gnu.gdb.bug,gnu.gcc.bug,gnu.g++.bug
Subject: Re: compile gdb with gcc -Wall
Message-ID: <25E7384D.23217@paris.ics.uci.edu>
Date: 25 Feb 90 01:43:41 GMT
References: <9002221656.AA09651@msm10.log-sv.se>
Reply-To: rfg@ics.uci.edu (Ronald Guilmette)
Distribution: gnu
Organization: UC Irvine Department of ICS
Lines: 19

In article <9002221656.AA09651@msm10.log-sv.se> gnu%msm10@log-sv.se writes:
>
>I compiled gdb with gcc-1.37 and -Wall.
>I have never seen such a mass of warnings.
>
>Could`nt you guys at least try to make the code gcc complaints free.

I have been praying for that to happen to *all* of the GNU software for
quite a long time.  Nobody seems to care.

Try compiling protoize with -Wall.  You should get zero warnings/errors.
That's even with the code fully function-prototyped!!

I consider -Wall one indicator of code quality.  Others apparently disagree.


// Ron Guilmette (rfg@ics.uci.edu)
// C++ Entomologist
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.