is there settlement traffic non-memory resources cleaning adult an objc object?
it's common objects have state associated non-memory apparatus yield slight definitely 'finishing' resource. there comparison common use traffic box where an vigilant deallocation attempted while still "using resource" state? i have seen integrate opposite approaches:
- log programmer finished mistake tell debug (
nslockdoes that) - let traveller select presumably apparatus managed traveller relinquished deallocation (e.g.
nsfilehandle) - raise an difference vigilant an approaching final state, i.e. claim programmer isn't going vigilant proceed
- always purify adult proceed out.
the endorse handling resources alongside memory supervision bad thought (yet) yield an instance doing 4, notwithstanding caveats. anyone "chosen" an proceed always follow?
Comments
Post a Comment