Re: ObjC in time-critical parts of the code
Re: ObjC in time-critical parts of the code
- Subject: Re: ObjC in time-critical parts of the code
- From: Ben Trumbull <email@hidden>
- Date: Sun, 18 Jan 2009 23:49:34 -0800
On Sun, Jan 18, 2009 at 9:23 PM, Ben Trumbull <email@hidden>
wrote:
Several work arounds exist. The easiest is to create a static C
member
function (yes, ObjC has member *functions* which most people
overlook).
Well no, it doesn't. ObjC has functions, by virtue of being a superset
of C, but it does not have "member functions". You can write functions
that are logically associated with a class, but this is a human
construct, not one that the compiler knows about.
Not sure what compiler you're using, but mine can tell the difference:
#import <Foundation/Foundation.h>
@interface Foo : NSObject {
@private id a;
}
@end
static id plainCFunction(Foo* f);
static id memberCFunction(Foo* f);
static id plainCFunction(Foo* f) {
return f->a;
}
@implementation Foo
static id memberCFunction(Foo* f) {
return f->a;
}
@end
/tmp/members/members.m: In function 'plainCFunction':
/tmp/members/members.m:12: warning: instance variable 'a' is @private;
this will be a hard error in the future
- Ben
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden