Re: [OT] Retain count riddle
Re: [OT] Retain count riddle
- Subject: Re: [OT] Retain count riddle
- From: Christopher Behm <email@hidden>
- Date: Tue, 30 Mar 2004 15:23:11 -0500
Well, sub in your arguments to the macro:
[[path lastPathComponent] retain];
[m_Path release];
m_Path = [path lastPathComponent];
If lastPathComponent returns a new object at each call (and it probably does, likely an autoreleased string), then you'd have your problem. Even if it didn't return a new object, it'd be bad practice to do it that way. I'm not macro guru, so I don't know if there's a way to get what you want either.
Chris
On Tuesday, March 30, 2004, at 02:49PM, Sailesh Agrawal <email@hidden> wrote:
>
So I had this bug the other day that I thought would make an interesting
>
riddle.
>
>
The code looked like this:
>
>
#define SAFE_SET(old, new) [new retain]; [old release]; old = new;
>
>
...
>
>
- (void) foo : (NSString*)path {
>
SAFE_SET(m_Path, [path lastPathComponent]);
>
}
>
>
Now the problem was any time I accessed m_Path my app would crash. This
>
isn't cocoa specific, I'm just dumb for using macros where I should have
>
been using a function. Can anyone guess what the problem is ?
>
>
good luck !
>
Sailesh
>
_______________________________________________
>
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.
_______________________________________________
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.