Re: Losing my memory - a caching problem?
Re: Losing my memory - a caching problem?
- Subject: Re: Losing my memory - a caching problem?
- From: Stuart Rogers <email@hidden>
- Date: Tue, 17 Aug 2010 23:00:02 +0100
On 17 Aug 2010, at 22:48, Sean McBride wrote:
> On Tue, 17 Aug 2010 22:20:55 +0100, Stuart Rogers said:
>
>>>> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
>>>> ...
>>>> [pool release];
>>>
>>> Have you tried using drain instead of release? That seems to be the
>> preferred way at this point, triggering GC collection if needed (I don't
>> know if your code is GC enabled, but if the library code is GC enabled,
>> then this will solve some of those problems)
>>
>> My app is uses retain/release - I have an aversion to garbage collection - so
>> (according to the documentation) drain will do exactly the same as release.
>
> Still, using drain is probably a good habit to get into. For example,
> the clang static analyzer flags using release on an autorelease pool as
> a warning.
Really? For me, after a clean build, Build & Analyse doesn't complain.
What warning do you get?
Stuart, Xcode v3.2.1 on OSX 10.6.4
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden