[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handles and Pointers [was: performance issues]

Subject: Re: Handles and Pointers [was: performance issues]
From: steve zellers <email@hidden>
Date: Wed, 30 Mar 2005 17:30:29 -0800
Delivered-to: email@hidden
Delivered-to: email@hidden

On Mar 30, 2005, at 5:18 PM, Laurence Harris wrote:

I can't help but wonder why it would be so inefficient. Care to share?

Well, you could measure it... or step through it in gdb. Last time I looked, it called malloc_size, then looked in another table based on that size to get where the actual size is stored. I think the malloc_size implementation is in open source, so that could give you an idea of *its* implementation (likely requiring a lot of scanning.)

GetPtrSize also works if you hand it a dereferenced handle, in which case it has to call RecoverHandle and GetHandleSize...

There is no way all that is going to be more efficient than keeping track of it yourself :-)

--smz

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden

References:
	>Re: Handles and Pointers [was: performance issues] (From: Laurence Harris <email@hidden>)

Prev by Date: Re: Handles and Pointers [was: performance issues]
Next by Date: what does shared window means in QuartzDebug?
Previous by thread: Re: Handles and Pointers [was: performance issues]
Next by thread: Re: performance issues
Index(es):
- Date
- Thread

Home