Hi Thomas > Which is something some people at Apple encourage not to do. The leading > underscore is seen as "Library implementors naming space" (also and > especially for method signatures) so your code might break when you use that > coding pattern. > > OTOH, enforcing would break many peoples codebase, so it is unlikely that > will ever happen.
There is no need to enforce anything on developers. All that is needed is to detect whether the ivar is @private and to respect that visibility. If an ivar is private, it should not be visible in the IB designer, regardless of whether it is of type id or not. This will not break anyone's code as most legacy code that required id-typed ivars to be visible in IB doesn't use visibility specifiers. 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
