This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Will 2.95.4 ship with new libobjc ?
- To: Bernd Schmidt <bernds at redhat dot com>
- Subject: Will 2.95.4 ship with new libobjc ?
- From: Nicola Pero <nicola at brainstorm dot co dot uk>
- Date: Fri, 6 Apr 2001 13:07:22 +0100 (BST)
- Cc: gcc at gcc dot gnu dot org
Hi Bernd -
here is a suggestion/request for gcc-2.95.4.
The current state of Objective-C support in gcc 3.x seems to be that -
* the compiler itself is broken (can't compile protocols);
* libobjc instead is in great shape and much better than the one which
ships with gcc 2.95.x.
Currently, most people using Objective-C will use a 2.x compiler, but
install the libobjc from the CVS HEAD (you find it packaged standalone on
the net).
Would it be possible to ship the newer libobjc with gcc 2.95.4 ? That
would make gcc-2.95.4 definitely the best existing choice for Objective-C,
and would simplify our life.
As far as I know, the newer libobjc is totally stable - more stable than
the one which ships with gcc-2.95.3 as some thread fixings have been done.
The main changes which have been done are:
* libobjc now builds as shared as well;
* importatnt fixes for threads;
* a couple of new useful hooks (harmless in all other respects) have been
added.
These changes are also the reason why we use the newer libobjc.
I have no notice of bugs in it. It is in quite widespread use (unlike the
gcc-3.x objective-c compiler which nobody uses since it doesn't work), so
it shouldn't be a risk at all to port it to gcc-2.95.4.