将对象设置为nil时不调用dealloc方法

TS.*_*.xy 3 objective-c ios

我有个问题.

我首先创建了一个扩展NSObject的对象,我提供了描述和dealloc方法的覆盖.这是我的Employee.m文件:

@implementation Employee
.....

-(NSString *)description
{
    return [NSString stringWithFormat:@"Employ ID: %d has $%d value of assets", [self     employeeID], [self valueOfAssets]];
}

-(void)dealloc
{   
    NSLog(@"deallocating.. %@", self);
    [super dealloc];
}
Run Code Online (Sandbox Code Playgroud)

在我的main.m中,我首先创建了一个NSMutableArray来保存Employee对象列表:

NSMutableArray *employees = [[NSMutableArray alloc] init];

for (int i =0; i< 10; i++)
{
    // Create an instance of Employee
    Employee *person = [[Employee alloc] init];

    // Give the instance varaible interesting values
    [person setEmployeeID:i];
    [employees addObject: person];
}
Run Code Online (Sandbox Code Playgroud)

最后我把员工定为零

employees = nil;
Run Code Online (Sandbox Code Playgroud)

我期望dealloc调用每个Employee对象的方法,我会看到一些日志,如:

deallocating.. Employ ID 0 has value.....
deallocating.. Employ ID 2 has value.....
....
Run Code Online (Sandbox Code Playgroud)

但是,我没有看到任何日志,如果我在dealloc方法上设置了断点,则断点永远不会被击中.

有什么想法吗?

Rob*_*Rob 8

几点意见:

  1. person = nil不会在非ARC代码中释放对象.它将在ARC代码中(至少如果它很强大).

  2. 在ARC中,当本地对象超出范围时,它们将自动为您释放.在非ARC中,不会为您释放超出范围的对象(如果您在其他地方没有其他对这些对象的引用,则最终会泄漏).

  3. 将项添加到可变数组将增加项的保留计数,因此即使您在非ARC代码中包含一个版本,该对象也不会被释放,直到保留计数降至零(不仅仅通过释放来完成)将对象添加到数组后,也将对象从数组中删除.

因此,鉴于这是非ARC代码,它可能是这样的:

- (void)testInNonArcCode
{
    NSMutableArray *employees = [[NSMutableArray alloc] init]; // employees retain count = +1

    for (int i =0; i< 10; i++)
    {
        //create an instance of Employee
        Employee *person = [[Employee alloc] init]; // person retain count = +1

        //Give the instance varaible interesting values
        [person setEmployeeID:i];
        [employees addObject: person];  // person retain count = +2
        [person release];  // person retain count = +1 (YOU REALLY WANT TO DO THIS OR ELSE OR NON-ARC PROGRAM WILL LEAK)
        // person = nil;   // this does nothing, except clears the local var that's limited to the for loop scope ... it does nothing to reduce the retain count or improve memory management in non-ARC code, thus I have commented it out
    }

    // do whatever you want

    [employees removeAllObjects]; // this will remove all of the person objects and they will have their respective retain counts reduced to 0, and therefore the Employee objects will be released

    [employees release]; // employees array's own retain count reduced to zero (and will now be dealloced, itself)
}
Run Code Online (Sandbox Code Playgroud)

在ARC代码中:

- (void)testInArcCode
{
    NSMutableArray *employees = [[NSMutableArray alloc] init]; // employees retain count = +1

    for (int i =0; i< 10; i++)
    {
        //create an instance of Employee
        Employee *person = [[Employee alloc] init]; // person retain count = +1

        //Give the instance varaible interesting values
        [person setEmployeeID:i];
        [employees addObject: person];  // person retain count = +2

        // person = nil;      // this would reduce person retain count to +1 (but unnecessary in ARC because when person falls out of scope, it will have it's retain count automatically reduced)
    }

    // do whatever you want

    [employees removeAllObjects]; // this will remove all of the person objects and they will have their respective retain counts reduced to 0, and therefore will be released

    // [employees release]; // not permitted in ARC
    // employees = nil;     // this would effectively release employees, but again, not needed, because when it falls out of scope, it will be released anyway
}
Run Code Online (Sandbox Code Playgroud)

  • 这应该是公认的答案.我不认为"改为ARC"正确地回答了这个问题,因为这个问题意味着这个人出于某种原因不使用ARC(这可能是故意的)而且这个答案是解释性的,并且还解释了ARC会是什么做的不同. (2认同)