• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Fix Depracated call in Apple Sample Code?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fix Depracated call in Apple Sample Code?


  • Subject: Re: Fix Depracated call in Apple Sample Code?
  • From: Finlay Dobbie <email@hidden>
  • Date: Fri, 3 Feb 2006 09:53:33 +0000

On 02/02/06, Jerry Krinock <email@hidden> wrote:
> on 06/01/26 16:52, Gregory Weston at email@hidden wrote:
> > Seems like the obvious answer is to fix the bug and then submit the
> > fix as part of the bug report. Any chance that the symbol for which
> > you're looking is __NSGetExecutablePath?
>
> No.  They are NSIsSymbolNameDefined and NSLookupAndBindSymbol:

Yes, which are used for dynamically looking up and binding a symbol.
In particular, the symbol they are looking for is
__NSGetExecutablePath, which appeared in 10.2.

It's probably unlikely that you're going to be targeting pre-10.2 in
this day and age anyway, so I'd just eliminate the dynamic lookup
altogether (and the fallback which relies on nasty implementation
details).

 -- Finlay
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Fix Depracated call in Apple Sample Code? (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Re: Objective-C or Objective-C++
  • Next by Date: Customized ruler type in my view
  • Previous by thread: Re: Fix Depracated call in Apple Sample Code?
  • Next by thread: Re: Binding NSPopupButton to a set of NSObjects
  • Index(es):
    • Date
    • Thread