Where does it say that protocols can't include class methods? If
there is documentation indicating as much then there is a bug
somewhere and I'd like to know about it.
The following works as expected -- the compiler complains mightily
about the lack of conformance to protocol Bob in class Fred.
@protocol Bob
+ (void) foo;
@end
@interface Fred : NSObject <Bob>
@end
@implementation Fred
@end
Got it working now!
I had
@protocol Bob
+ (Bob *)sharedBob; // error: syntax error before 'Bob'
@end // warning: '@end' must appear in an @implementation context
@interface Fred : NSObject <Bob>
...
@end
but it needs to be:
@protocol Bob
+ (NSObject<Bob> *)sharedBob;
@end
However, protocols are not generally used to hide implementation
details. It sounds more like you want a combination of public and
private headers / declarations.
Definitely sounds like that. Basically I have a framework entry
(public header)
@interface Bob {
@private
some ivars here
}
+ (Bob *)sharedBob;
- (void)someMethods;
@end
And I would rather have it look like this in public.
@interface Bob
+ (Bob *)sharedBob;
- (void)someMethods;
@end
Still I need those ivars in private though.
For Cocoa, functionality that is supported is made available through
public headers. Functionality that is internal to Cocoa is
encapsulated in private headers that declare said private interfaces
through a combination of categories, class extensions and full-on
class declarations.
Any pointers on how this is done?
cheers
--
Torsten
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
