3 ms·
For me "if you malloc, then you must free" is much harder, because you have to know whether ownership was passed to you, who else might be using object when you
by pornel 16y ago
For me "if you malloc, then you must free" is much harder, because you have to know whether ownership was passed to you, who else might be using object when you free it, etc.
In Objective-C there's no owner, everyone borrows objects. You increase retain count (if you want to hold object for longer than lifetime of a function), and you decrease retain count when done.
And there are few methods to increase (retain, init, copy, new, property assignent) and few to decrease count (release, autorelease, nil property assignment).
To me it's that simple.
- schumihan 16y agoReference count based GC? How would you deal with circular reference?
- eru 16y agoYou don't. You'd avoid creating circular structures as much as possible. You can get pretty far that way.
- schumihan 16y agoIt's very difficult to avoid it when thing goes complicating. A may reference B, B may reference C, ... and somewhere, X may reference back to A. If this strategy makes sense for big project, many hackers work with C++ can use it either, as the performance overhead is very low. But in the real world, reference-count based GC just has limited usage.
- eru 16y ago> But in the real world, reference-count based GC just has limited usage. And in theory it doesn't fare much better. Proper garbage collection can have better performance, and does the Right Thing.
- xsmasher 16y agoRetain your children but not your parents; or do you mean a group of "peers" who retain each other? They should probably be in some kind of collection that retains them All.