From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1025b4,1d8ab55e71d08f3d X-Google-Attributes: gid1025b4,public X-Google-Thread: 103376,1efdd369be089610 X-Google-Attributes: gid103376,public From: Bill Gribble Subject: Re: what DOES the GPL really say? Date: 1997/07/08 Message-ID: <87k9j1d0t5.fsf@firetrap.csres.utexas.edu>#1/1 X-Deja-AN: 255521231 References: <5ph4g5$sbs$1@vixen.cso.uiuc.edu> <5pim4l$5m3$1@news.nyu.edu> <5pthps$v0b$1@news.nyu.edu> Organization: The University of Texas at Austin Newsgroups: comp.lang.ada,gnu.misc.discuss Date: 1997-07-08T00:00:00+00:00 List-Id: kenner@lab.ultra.nyu.edu (Richard Kenner) writes: > This isn't a prudent course of action, since most bugs on a mature > program such as GCC tend to be ones that have *not* already been > discovered. gcc isn't a good example for your argument... IMO most of the bugs in gcc are well-known ones in the immature parts of the program (the c++ parts, in gcc's case) rather than undiscovered ones (of which I'm sure there are still plenty) in the more-mature parts. Bill Gribble