This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Find more ObjC methods
- From: Ziemowit Laski <zlaski at apple dot com>
- To: Markus Hitter <mah at jump-ing dot de>
- Cc: Ziemowit Laski <zlaski at apple dot com>, Alexander Malmberg <alexander at malmberg dot org>, discuss-gnustep at gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Fri, 3 Oct 2003 11:41:47 -0700
- Subject: Re: PATCH: Find more ObjC methods
On Friday, Oct 3, 2003, at 02:45 US/Pacific, Markus Hitter wrote:
Am Freitag, 03.10.03 um 04:10 Uhr schrieb Alexander Malmberg:
Ziemowit Laski wrote:
[snip]
in the long run, the compiler should stop distinguishing @interfaces
from
@implementations (since the former are merely forward declarations
for the latter).
I've always considered this a feature. The @interface is the public
interface for an @implementation. Thus, methods that appear only in
an implementation are private to that implementation.
Thing is, the "private" @implementation-only methods will still be
found by the runtime. :-)
It will stay there as a feature unless you get rid of header files at
all and #include the whole source when using a library.
Sorry for not stating my thoughts more clearly. I wasn't thinking of
changing the language (or its usage) at all. :-) All I was saying
that the ObjC front-end need not construct separate data structures
(_internally_) for @interfaces and @implementations; there is a lot of
useless duplication going on...
--Zem
-------------------------------------------------------------
Ziemowit Laski 1 Infinite Loop, MS 301-2K
Mac OS X Compiler Group Cupertino, CA USA 95014-2083
Apple Computer, Inc. +1.408.974.6229 Fax .5477
--------------------------------------------------------------
Ziemowit Laski 1 Infinite Loop, MS 301-2K
Mac OS X Compiler Group Cupertino, CA USA 95014-2083
Apple Computer, Inc. +1.408.974.6229 Fax .5477