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: Helge Hess <helge dot hess at opengroupware dot org>
- Cc: Alex Perez <aperez at student dot santarosa dot edu>, gcc at gcc dot gnu dot org, Adrian Robert <arobert at cogsci dot ucsd dot edu>, Richard Earnshaw <rearnsha at gcc dot gnu dot org>, gnustep-dev at gnu dot org, Robert Dewar <dewar at adacore dot com>, Mark Mitchell <mark at codesourcery dot com>, Zack Weinberg <zack at codesourcery dot com>, discuss-gnustep at gnu dot org
- Date: Tue, 25 Jan 2005 18:44:01 +0100
- Subject: Re: Objective-C bugs and GCC releases
- Organization: SUSE Labs
- References: <20050124224245.24868.qmail@web41623.mail.yahoo.com> <200501251735.51170.stevenb@suse.de> <0A7059BA-6EF8-11D9-ACCF-000D93C1A604@opengroupware.org>
On Tuesday 25 January 2005 18:39, Helge Hess wrote:
> On Jan 25, 2005, at 17:35, Steven Bosscher wrote:
> > 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 don't understand what you are saying. For one you seem to agree with
> me that one shall not break others code and even push that opionion
> towards ObjC++ guys, but at the same time this is done by C/C++
> contributors to ObjC.
> That doesn't seem to make a lot of sense to me.
Will you stop accusing everyone of breaking ObjC? This is *not* what
happened. The ObjC front end itself was broken, and not by changes to
the C/C++ front end, it was broken well before and it just happened to
work.
It is like driving in a car with a broken steering wheel. At one point
there will be a turn and you will run off the road. That's not because
the turn in the road should not have been there, you should just have
your car fixed.
In this case the car is the ObjC front end, and it was not fixed before
GCC took a turn.
Gr.
Steven