Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Handles and Pointers [was: performance issues]

Surely an Apple engineer noticing that something is inefficient and commenting about it on a public list doesn't mean that it should automatically go to the top of Apple's list of priorities.

"Dropping the ball again" is a rather harsh and I think unwarranted charge in this case.

Really, Steve's comment should have read "if Shark indicates massive CPU time spent in GetPtrSize" instead of "if at all possible"...

Daniel

On Mar 31, 2005, at 8:49 AM, Laurence Harris wrote:
On 3/30/05 3:06 PM, steve zellers didst favor us with:
Also, I saw another comment about using GetPtrSize - if at all possible, you
should maintain the size of your allocation if you'll think you'll need it
later.  GetPtrSize is rather inefficient.
The next question then, is why isn't the NewPtr mechanism implemented as
efficiently as Steve thinks my substitute would be? If that were the case
then it would be a non-issue. All the code currently using GetPtrSize would
be more efficient and lots of developers could so something more productive
with their time instead of having to worry about this kind of stuff and
changing code. Apple drops the ball again. 

_______________________________________________
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>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.