Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
- Subject: Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
- From: Scott Anguish <email@hidden>
- Date: Sat, 6 Dec 2003 14:58:14 -0500
On Dec 6, 2003, at 2:42 PM, Simon Stapleton wrote:
From: Finlay Dobbie <email@hidden>
Subject: Re: Toll Free Bridging, wrapping the SearchKit, and One-Way
Bridging
Date: Thu, 4 Dec 2003 23:44:16 +0000
To: Scott Anguish <email@hidden>
On 4 Dec 2003, at 06:16, Scott Anguish wrote:
Second, there isn't a gain. When Apple toll-free bridges something
in CF, there is a gain because Apple doesn't need to write and test a
second set of APIs, we don't need to doc them, and it's more
straightforward. You're writing the second set of APIs yourself, so
you gain nothing.
The APIs, yes, you write yourself. But the underlying implementation
is 'for free'. So you _do_ gain something. For example, in bridging
CFXML, I got access to an existing (read 'installed as a part of OSX')
framework in ObjC, as opposed to having to use nasty Carbon stuff or
having to install (for example) expat + objc libraries written by
someone else.[1][2]
Sure.. but toll free bridging in this case is no different than
wrapping those carbon calls in an Objective-C API. You still have to
write the code...
If you wrap it in Objective-C, you still get to use a part of the
installed system..
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.