[Bug libobjc/47173] both objc_lookUpClass and objc_lookup_class are exported symbols

["nicola at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47173

Nicola Pero <nicola at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |nicola at gcc dot gnu.org
         Resolution|                            |INVALID

--- Comment #2 from Nicola Pero <nicola at gcc dot gnu.org> 2011-01-06 14:49:43 UTC ---
Yes.  In GCC 4.6, libobjc has lots of "duplicates", because it supports both
the "Traditional" and "Modern" GNU Objective-C runtime APIs (see the GCC doc
for the explanation), which obviously overlap in functionality.

In GCC 4.7, we'll remove the traditional one and get rid of the duplicates.

The example you chose, objc_lookup_class(), is particular, though, because
objc_lookup_class() is part of the ABI too, ie, it is used by the compiler when
compiling Objective-C method invocations.  So even in GCC 4.7 we may want to
keep it around in libobjc if we want to be able to load modules compiled with
an older compiler.

Thanks