> I'm new at this too, so perhaps I am completely off here. My guess is that it > isn't the const that is messing this up, but the non-class type. The problem > I see is that "frame" is a pointer to an objc_object and objc_objects aren't > the same as NSObjects (but, like I said, I'm new, so maybe they are > interchangeable here). Does it work if you try declaring frame as a > NSObject<FrameProtocol> instead of an id<FrameProtocol>? It was your suggestion here that got me thinking along the right track, in fact, but that declaration does not actually make any sense as far as I know - that is not the normal way of declaring a generic pointer that conforms to a protocol, and it leads to a whole load of warnings/errors elsewhere in the code..._______________________________________________
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 arch...@mail-archive.com
