FROM : Robert Nikander
DATE : Mon Nov 05 19:17:07 2007
On Nov 5, 2007, at 12:37 PM, Shawn Erickson wrote:
> On 11/5/07, Robert Nikander <<email_removed>> wrote:
>
>> So what is different about calling through the NSInvocation that
>> causes the error message?
>
> As a test try sending a retain message to alloced object after each of
> the following...
>
> b = [NSButton alloc];
> b = objc_msgSend(button_class, alloc_sel);
Doh! Thanks, I think that answers it. It makes sense that
NSInvocation would retain object return values, and is thus unusable
for calling "alloc". I'm used to garbage collection...
Rob
DATE : Mon Nov 05 19:17:07 2007
On Nov 5, 2007, at 12:37 PM, Shawn Erickson wrote:
> On 11/5/07, Robert Nikander <<email_removed>> wrote:
>
>> So what is different about calling through the NSInvocation that
>> causes the error message?
>
> As a test try sending a retain message to alloced object after each of
> the following...
>
> b = [NSButton alloc];
> b = objc_msgSend(button_class, alloc_sel);
Doh! Thanks, I think that answers it. It makes sense that
NSInvocation would retain object return values, and is thus unusable
for calling "alloc". I'm used to garbage collection...
Rob
| Related mails | Author | Date |
|---|---|---|
| Robert Nikander | Nov 5, 05:07 | |
| Gorazd Krosl | Nov 5, 16:15 | |
| Clark Cox | Nov 5, 16:43 | |
| Robert Nikander | Nov 5, 17:17 | |
| Shawn Erickson | Nov 5, 18:37 | |
| Robert Nikander | Nov 5, 19:17 |






Cocoa mail archive

