On Jul 13, 2008, at 10:37 PM, Bill Bumgarner wrote:
And, no, exchanging class methods is not a typical pattern to be
employed when developing a Cocoa application. In particular,
replacing or exchanging method implementations found in Apple
frameworks is completely unsupported and will quite likely break in
the future.
b.bum
I fully admit that the use of the private methods -[NSApplication
setAppleMenu:] and -[NSMenu _setMenuName:] is completely unsupported
and may break in the future, though I hope that they don't and that
in fact Apple provides public API for this functionality.
On the other hand, the function method_exchangeImplementations() just
became public API in Leopard, so I don't see how that can break
anytime soon. It's not much different than subclassing or
'categorizing'.
-Jeff
_______________________________________________
Cocoa-dev mailing list ([email protected])
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]
