Message-ID: <3633E644.420F30A2@montana.com>
Date: Sun, 25 Oct 1998 20:02:28 -0700
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.5b2 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: construction has been delayed due to somebody's stupidity (most 
 likely my own)
References: <5zeY1.843$SI2 DOT 270 AT news DOT cwix DOT com> <gunaalubzrpbz DOT f1bmi21 DOT pminews AT news DOT avnl1 DOT nj DOT home DOT com> <3631E505 DOT 4773CBD3 AT montana DOT com> <gunaalubzrpbz DOT f1cmla2 DOT pminews AT news DOT avnl1 DOT nj DOT home DOT com> <36329321 DOT 21F4ACAD AT montana DOT com> <gunaalubzrpbz DOT f1eman4 DOT pminews AT news DOT avnl1 DOT nj DOT home DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com



Mike Ruskai wrote:
> 
> That would be annoying in the extreme.  Do you really want to see a warning
> for every header file that declares but not defines functions (e.g. the
> entire C library)? 

No, on further reflection you are right. I learned a new trick out of
it. When
declaring a class, I sometimes declare member functions that I
anticipate i'll need. 
I've always assumed that I had to stub them out in the definition file,
but that 
isn't the case.

I will admit I prefer to know about unused variables. I tend to leave a
few strays
when I restructure a function that I would as soon clean up. Personal
tastes. I guess
thats why there are more -W switches than my fading brain can ever
remember.