Re: objc is badly broken

[Nicola Pero <n dot pero at mi dot flashnet dot it>]

> It's failing a good percentage of its test suite 

Ahm - I only have nested-1.m and protocol.m failing - it's not that
much - though they are very important tests and the fix is probably
non trivial.

np-1.m, np-2.m, bycopy-1.m, bycopy-2.m are fixed by recent patches not
yet applied - see `Bug in Objective-C Compiler Found' thread on
gcc-bugs.


> I fixed one problem 

Great !

> but then got into a morass of problems relating to internally-generated 
> functions and didn't understand the code enough to get further.  Here's 
> my patch so far.

If you can fix them that would be *great*.  I can help you - most of
my company's software (which is a lot) is written in Objective-C and
compiled with gcc and they are very happy if I spend work time helping
to fix the Objective-C support in gcc - but I don't know much of the
gcc internals yet, so the thing I can do best now is testing changes,
providing tests and tracking problems.  If I can help you with some of
these things, please tell me as I can do that immediately.

Anyway - I'll have a look at this part in next days and see what I can
understand of this stuff - but I know it'll take me quite a lot to fix
gcc code if I am to do it alone - as I know nearly nothing of gcc
internals.


> I think this should either be fixed or objc disabled.

It must be fixed.

I'll ignore the proposal of disabling objc since I think it was just a
provocation.  But I'll rip your head if you say it again.