RE: "introduce no new bootstrap warning" criteria. was: Loop iv debugging patch

[David Korn <dkorn at pixelpower dot com>]

>Obviously this cannot happen over night, but I think it is a very
>useful goal. There is something about zero warnings that is considerably
>more useful than "few" warnings.

  Seconded.  We adhere to this standard in my daily work, although we are
flexible about it if the circumstances seem to justify.  Hard experience
has shown us that the more warnings fly by during a build, the less likely
anyone is to pay attention and notice new ones that actually mean something
serious.  It's proved to be a source of bugs, so we decided to stop it.

  Of course it may or may not be an attainable goal considering the number
of targets that gcc builds for, but that's a practical rather than
theoretical problem ......

     DaveK
-- 
The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online
community." 


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************