On 1/27/10 12:01 PM, Jean-Daniel Dupas said: >I also prefer this approach but it should be use with care as >sometimes, a framework in a previous OS version "exports" private >function/method with the same name but with a different behavior. > >So, if you test for function existence, it always returns true, even on >the OS version which contains a non-working version of the function. > >This is rare, but I remember some cases in the Security framework which >exports symbols declared as private and not implemented in an OS version >and change these symbols as public in the following major version.
This has bitten me too. If Apple would consistently name their private methods with an underscore, this would not be a problem. -- ____________________________________________________________ Sean McBride, B. Eng [email protected] Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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]
