This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Objective-C bugs and GCC releases
- From: Steven Bosscher <stevenb at suse dot de>
- To: gcc at gcc dot gnu dot org
- Cc: Helge Hess <helge dot hess at opengroupware dot org>, Richard Earnshaw <rearnsha at gcc dot gnu dot org>, discuss-gnustep at gnu dot org, Robert Dewar <dewar at adacore dot com>, gnustep-dev at gnu dot org, Adrian Robert <arobert at cogsci dot ucsd dot edu>, Alex Perez <aperez at student dot santarosa dot edu>, Mark Mitchell <mark at codesourcery dot com>, Zack Weinberg <zack at codesourcery dot com>
- Date: Tue, 25 Jan 2005 17:35:50 +0100
- Subject: Re: Objective-C bugs and GCC releases
- Organization: SUSE Labs
- References: <20050124224245.24868.qmail@web41623.mail.yahoo.com> <1106667168.26277.23.camel@pc960.cambridge.arm.com> <1D28CFDA-6EEC-11D9-ACCF-000D93C1A604@opengroupware.org>
On Tuesday 25 January 2005 17:13, Helge Hess wrote:
> On Jan 25, 2005, at 16:32, Richard Earnshaw wrote:
> > You're forgetting that this is a volunteer project. We can't force
> > developers to work on something they don't want to work on.
>
> Every project has rules which need to be followed, even by volunteers.
> And in the past is was usual behaviour, if not unwritten law, not to
> break other people's stuff.
Nobody broke other people's stuff. Other people's stuff was itself
broken and it just happened to work with some luck.
> Sure, modifications are allowed, but if you change something you need
> to take care it doesn't affect other parts _of the same project_. And
> cc1obj _is_ (still?) a part of GCC.
So is C/C++, so perhaps you can convince the people pushing ObjC++
that your argument is valid. We have already tried that without luck.
> I think thats pretty much the usual way how all projects work.
It is also how GCC works.
> Its a
> matter of fairness with the other project members.
You seem to imply some project members treat objc unfair, but you just
so miss the point.
Gr.
Steven