Hi Roland Le 13 mars 2010 à 12:13, Roland King a écrit :
> I don't know if Joanna was suggesting you couldn't make anything available to > IB by making it an IBOutlet, I took it that she was saying the old > 'compatibility mode' of having any variable of type 'id', even if not an > IBOutlet, be visible in IB would not be broken if you restricted it to those > variables of type id which were not @private, because @private post-dates any > code which should be depending on that old hack. Absolutely my point. There is no problem of backwards compatibility because the two "technologies" do not clash. > I sort of agree, but I also sort of don't have this issue, never had a > variable of type id in my class. If I did, I'd probably make it NSObject* and > .. does that make it stop? My reason for using id is because I want to hold a delegate and call methods on it without compiler warnings. Or have I got the wrong idea there? Joanna -- Joanna Carter Carter Consulting _______________________________________________ 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
