This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Proposal to evaporate OBJC_INT_SELECTORS


Sounds fine with me, GNU Objective-C never used them anyway.

Just as a curiosity, how do selectors look like these days in Apple's
Objective-C runtime? They used to be only a reference into a
hash-table of selector names, with no types associated. This contrasts
with the GNU Objective-C runtime, where a selector is a pointer to
both a selector id and the types of its arguments and return value.

Thanks,
Ovidiu

On Thu, 22 Mar 2001 15:29:41 -0800, Stan Shebs <shebs@apple.com> wrote:

> For a very long time, GCC's Objective-C frontend has included a
> documented tm macro OBJC_INT_SELECTORS that is to be defined if
> method selectors should be of type int rather than of type
> struct objc_selector * (this matters because ObjC programs can
> manipulate selectors and such at runtime).
> 
> However, this macro is never ever set by anything at all. The
> oldtimers at Apple (including Steve Naroff, who originally
> contributed ObjC to GCC) vaguely remember a time when method
> selectors were not pointers, but it would have been quite some
> time ago, perhaps as much as ten years, in GCC 1.x days.
> 
> So in order to simplify comprehension and maintenance of the ObjC
> frontend, I propose to delete the macro and all references to
> it.  If anybody knows of a reason to save it, now would be a
> good time to speak up!
> 
> Stan
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]