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=-0.5 required=5.0 tests=BAYES_00,INVALID_MSGID, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 103376,1efdd369be089610 X-Google-Attributes: gid103376,public X-Google-Thread: 1025b4,1d8ab55e71d08f3d X-Google-Attributes: gid1025b4,public From: David Kastrup Subject: Re: what DOES the GPL really say? Date: 1997/07/09 Message-ID: #1/1 X-Deja-AN: 255731102 References: <5ph4g5$sbs$1@vixen.cso.uiuc.edu> <5pim4l$5m3$1@news.nyu.edu> <5pthps$v0b$1@news.nyu.edu> Organization: Institut fuer Neuroinformatik, Ruhr-Universitaet Bochum, Germany Newsgroups: comp.lang.ada,gnu.misc.discuss Date: 1997-07-09T00:00:00+00:00 List-Id: kenner@lab.ultra.nyu.edu (Richard Kenner) writes: > In article Olivier.Galibert@mines.u-nancy.fr (Olivier Galibert) writes: > >In article <5pim4l$5m3$1@news.nyu.edu>, Richard Kenner wrote: > >>There's absolutely nothing wrong with pointing out that it's harmful > >>to the GNAT community for pre-releases to be widely distributed. The > >>FSF itself (and Richard Stallman personally) has an extremely strong > >>similar view about pre-releases of GCC. > > > >With the immediate side effect that most people won't even try to fix > >bugs which may already have been fixed. And most of the time don't even > >bother to report them because of the "I'll try again in 6 months with > >the new release and then I'll see" effect. > > 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. With all due respect, please look at the bug report data base. More than half of the bugs I reported since gcc 2.5.something are still pending correction. It might well be that they have been fixed for years now, but the last major release of gcc (2.7.0) was made more than two years ago. Actually, for a few of them I got a message, I believe some time last year, "this will be fixed in 2.8.0". Considering the amount of bug reports piled up for gcc-2.7 already, when gcc-2.8.0 is supposed to be vastly overhauled in quite a few areas, I don't think it actually very useful anymore to write bug reports for a software which has undergone major changes in the last few years. Note that this applies largely to the g++ frontend which has been under the heaviest changes in the last few years. The backend, fortunately, is somewhat more stable. I got it to produce illegal code in some of my bug reports as well, but it might have got fed bad information from the C++ frontend. So if you manage to get bad code or error messages or so from compiling ANSI C, or perhaps Ada, a bug report might not be as hopeless as for g++. -- David Kastrup Phone: +49-234-700-5570 Email: dak@neuroinformatik.ruhr-uni-bochum.de Fax: +49-234-709-4209 Institut f�r Neuroinformatik, Universit�tsstr. 150, 44780 Bochum, Germany