home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!allegra!alice!ark
- From: ark@alice.att.com (Andrew Koenig)
- Newsgroups: comp.lang.c++
- Subject: Re: Destruction of temporaries
- Message-ID: <23598@alice.att.com>
- Date: 1 Sep 92 05:12:54 GMT
- Article-I.D.: alice.23598
- References: <rmartin.715004480@thor> <23583@alice.att.com> <rmartin.715101472@thor> <1992Aug29.184025.328@frumious.uucp> <rmartin.715267769@thor>
- Reply-To: ark@alice.UUCP ()
- Organization: AT&T Bell Laboratories, Murray Hill NJ
- Lines: 15
-
- In article <rmartin.715267769@thor> rmartin@thor.Rational.COM (Bob Martin) writes:
-
- > Ideed. But I think the warning is still useful.
-
- The unfortunate reality is that I have seen a number of development
- projects that have an inflexible rule -- no warnings allowed! That is,
- they will not allow their people to ship any code that generates warnings.
-
- Thus, giving a compiler warning for a construct is equivalent to
- banning it for those projects.
-
- Warnings had better be right almost all the time.
- --
- --Andrew Koenig
- ark@europa.att.com
-