Re: objective-c / cocoa efficiency
Re: objective-c / cocoa efficiency
- Subject: Re: objective-c / cocoa efficiency
- From: Scott Stevenson <email@hidden>
- Date: Tue, 8 Mar 2005 15:01:01 -0800
On Mar 8, 2005, at 2:18 PM, Barton J. Friedland wrote:
Can someone enlighten me here? I have written my code as per the Apple
guidelines as I understand them. Is there some secret horrible
inefficiency with Cocoa and / or Objective-C that I should know about
in order to satisfy the needs of this type of programmer?
Without seeing code, it's hard to say what the right thing is to do in
your situation. Apple's guidelines are just that, guidelines. They're
designed to point you in the right direction, not provide solutions for
every scenario.
There are certainly times when it makes more sense to use static,
lower-level C functions and structures to accomplish tasks (and
vice-versa). Knowing when to do this simply takes some experience.
The solution in this case may be as simple reducing your usage of
autorelease, or adding additional autorelease pools. The idea is to
optimize the bits of code that get called most frequently.
It also could be that the individual you're working with doesn't know
Cocoa and is misjudging the impact of your code, but there's simply
know way to know that without more details.
Also, what kind of profiling tools could I use to prove these
statements
as either true or false?
Apple's Shark and ObjectAlloc tools are good.
- Scott
--
http://treehouseideas.com/
http://theocacao.com/ [blog]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden