Re: what DOES the GPL really say?

[dewar@merv.cs.nyu.edu (Robert Dewar)]

<<I think you underestimate the people on that project.  At best, this will
become a quite stable release which will provide the free user community
with a stable, working gcc which can do RISC scheduling and which has
useful C++ templates.  The FSF, to whom all changes are assigned, can
then integrate them into 2.8 in whatever way they please.>>


Stability can only be achieved by being very careful and selective about
what changes are made. If that is the intention of the egcs project, then
that's too bad, since it seems to me the goals of a very free development
environment are better met by letting people experiment freely. If someone
has a neat bit of code that is 90% operational, and not very well documented,
then you certainly can't let it in to a building process that is aiming
at stablity, but the feature might still be very interesting to incorporate
and let people play with.

For example, during the recent round of development of exception handling
stuff for GCC, the developers on more than one occasion sent messages to
the effect of "well it is 90% working now, so why not go ahead and put it
in?" Quite approipriately, this was not considered to be in sufficiently
good shape to put into the mainline gcc development sources, but I would
hope that it WOULD be considered appropriate to put it into the egcs
project development, even if it were incomplete, not fully documented etc.

I don't think this has anything to do with the quality of people on the
project, it has to do with the fundamental goals. Perhaps I have 
misunderstood them, or perhaps they are not exactly clear yet.

Robert