• 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: Why is NSString->FSRef so hard?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why is NSString->FSRef so hard?


  • Subject: Re: Why is NSString->FSRef so hard?
  • From: Andy Lee <email@hidden>
  • Date: Thu, 30 Apr 2009 08:36:05 -0400

On Apr 30, 2009, at 4:52 AM, Kyle Sluder wrote:
In other words, why not just use the damn API?  It's not like you need
to deposit a coin to make a function call.

If you did, we wouldn't have toll-free bridging.

--Andy

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >Re: Why is NSString->FSRef so hard? (From: ERG Consultant <email@hidden>)
 >Re: Why is NSString->FSRef so hard? (From: Kyle Sluder <email@hidden>)

  • Prev by Date: Re: Bindings + NS{Secure}TextField validation -> coerced value is not used
  • Next by Date: NSTextView append Text help
  • Previous by thread: Re: Why is NSString->FSRef so hard?
  • Next by thread: Multiple cell in a table column
  • Index(es):
    • Date
    • Thread