Re: Could it really move? (Carbon Memory Manager)
Re: Could it really move? (Carbon Memory Manager)
- Subject: Re: Could it really move? (Carbon Memory Manager)
- From: Chris Hanson <email@hidden>
- Date: Sat, 19 Oct 2002 17:30:48 -0500
At 9:10 AM -0700 10/19/02, Chris Gehlker wrote:
Is the Carbon memory manager is really implemented in this
situation, requiring HLock and friends, or is it just a
compatibility layer?
It's a full implementation of the Memory Manager.
It's much, much, much less likely to move memory; the only time it's
likely to move memory is when a Handle is resized. However, the
contract exposed by the API is still that you need to lock handles
before dereferencing them.
So you still need to use the HLock/HGetState/HSetState pattern, since
Apple could decide tomorrow to change the implementation to move
memory more often and it would be valid the way the API is defined.
-- Chris
--
Chris Hanson | Email: email@hidden
bDistributed.com, Inc. | Phone: +1-847-372-3955
Making Business Distributed | Fax: +1-847-589-3738
http://bdistributed.com/ | Personal Email: email@hidden
_______________________________________________
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.