Re: Giving the CPU a break...
Re: Giving the CPU a break...
- Subject: Re: Giving the CPU a break...
- From: Sherm Pendley <email@hidden>
- Date: Tue, 19 Nov 2002 23:00:36 -0500
On Monday, November 18, 2002, at 02:04 PM, Buzz Andersen wrote:
My question is: is there a good way for me to give the CPU a break and
make the computer more responsive during this loop without compromising
performance significantly?
Are you sending messages inside of this loop? If so, you could eliminate
some overhead from that, by using NSObject's methodForSelector: to get a
direct pointer to the implementation (that is, an IMP) for the method.
From the example, you'd replace this:
while ( ![target isEqual: someObject] ) {
...
}
with this:
BOOL (*test)(id, SEL, id);
test = (BOOL (*)(id, SEL, id))([target methodForSelector:
@selector(isEqual:)];
while ( !test(target, @selector(isEqual:), someObject) ) {
...
}
As you can see, the replacement is a bit harder to read. I'd benchmark
both alternatives, to be sure that the added performance is enough to
justify the loss in maintainability.
sherm--
If you listen to a UNIX shell, can you hear the C?
_______________________________________________
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.