Re: Update Cocoa object from callback
Re: Update Cocoa object from callback
- Subject: Re: Update Cocoa object from callback
- From: Kurt Revis <email@hidden>
- Date: Tue, 20 May 2003 21:08:17 -0700
On Tuesday, May 20, 2003, at 03:47 PM, Robert Grant wrote:
Wasn't there kind of a big flame out a while ago about doing work in
these threads? I remember posting about using NSNotifications to alert
the main thread and there was a big discussion about how to ensure
that no memory was malloc'd and that the thread wasn't blocked/delayed
etc.
So I'm surprised to see things like Autorelease pool allocations etc
(surely a malloc happens underneath) being recommended in the
callback....
Has the policy changed?
I don't think the policy has changed. It's still what you need to do
to make a really good, professional app with the best possible timing.
But if you are not an expert at coding multithreaded "real-time" apps,
or are just hacking around and want to get things working quickly, you
can cut a few corners and still get results that more-or-less work.
--
Kurt Revis
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.