It looks like it was expanded in 10.5, then, but 10.4 and prior use the
16-bit variables. Regardless of whether it handles overflows or not, my
little joke was meant to illustrate that too many developers (generally
speaking) think that resources (generally speaking) are unlimited and
put no thought into what to do if an error occurs or how to handle
requirements that are potentially huge. I'm not saying those on this
list think this way, but when people say that there's no cost to this or
that approach, I just want to say, "Get thee a computer science degree!"
Michael Ash wrote:
On Sat, Jul 12, 2008 at 1:24 PM, Marcel Weiher <[EMAIL PROTECTED]> wrote:
No, the inline reference count is available for all CF objects, and not
limited to 64 bit.
What version of the structure are you looking at? For example
http://www.cocoadev.com/index.pl?HowToCreateTollFreeBridgedClass shows this
version, which matches what I got from opensource.apple.com
I was looking at:
http://www.opensource.apple.com/darwinsource/projects/apsl/CF-476.10/CFRuntime.h
It defines:
typedef struct __CFRuntimeBase {
uintptr_t _cfisa;
uint8_t _cfinfo[4];
#if __LP64__
uint32_t _rc;
#endif
} CFRuntimeBase;
I guess this isn't the right one, then.
To Gary, about 16-bit refcounts, I'd imagine that there's some logic
in there where if you hit 0xFFFF, it considers that to be a flag to
use an external refcount instead, at the cost of some speed.
Mike
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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]
