The reference counting mechanism does that for you.
引用计数机制为您完成内存管理任务。
The most straightforward garbage collection strategy is reference counting.
最直观的垃圾收集策略是引用计数。
It requires that you never forget to call the reference counting functions.
要求您永远不要忘记调用引用计数函数。
Since reference counting is so simple, most programmers implement it themselves rather than using libraries.
由于引用计数是如此简单，大部分程序员都自已去实现它，而不是使用库。
In a reference counting system, each object referenced maintains a count of how many objects are referencing it.
在引用计数系统，每个所引用的对象都会保留一个计数，以获悉有多少对象正在引用它。
There are several basic strategies for garbage collection: reference counting, mark-sweep, mark-compact, and copying.
有几种垃圾收集的基本策略：引用计数、标记-清除、标记-整理 (mark-compact)和复制。
However, you must remember to run the reference counting functions whenever you are using a reference-counted data structure.
不过，当您使用某个采用引用计数的数据结构时，您必须记得运行引用计数函数。
In a reference counting system, however, neither of the objects can be destroyed, because the reference count never reaches zero.
而在引用计数系统，这两个对象都不能被销毁，原因是引用计数永远不能为零。
Besides garbage collection, two other approaches are commonly used to deal with the problems of aliasing: reference counting and ownership management.
除了垃圾收集之外，通常还有其他两种方法用于处理别名问题：引用计数和所有权管理。
In a hybrid system, where both garbage collection and reference counting are being used, leaks occur because the system fails to identify a circular reference.
在同时使用了垃圾收集和引用计数的混合系统中，将会发生泄漏，因为系统不能正确识别循环引用。
InfoQ: MacRuby allows to AOT compile Ruby code - but is it possible to opt out of the Garbage Collector, ie. is there a way to just use Objective-C's reference counting memory management?
InfoQ：MacRuby允许使用AOT编译Ruby代码，那么，有没有可能不使用垃圾收集器，即能否仅仅使用Objective - c的引用计数内存管理？
The true challenge of this project was to take the existing reference counting system and move it over to the mark and sweep model in the existing code base without breaking old content.
这个项目真正的挑战在于替换：必须在已有代码基础上，把引用计数系统整个换成标记-扫描系统，而完全不破坏过去的内容。
Reference counting also has difficulties with structures having circular references.
引用计数也难以处理发生循环引用的数据结构。
Reference counting on objects and managing multiple interfaces on a single object are both useful concepts.
基于对象的引用计数和基于单一对象的多重接口管理都是有用的概念。
This is a Deferred Reference Counting (DRC) mechanism combined with an incremental, conservative mark/sweep collector.
它采用了一种延迟引用计数（Deferred Reference Counting，DRC）机制，并结合一个增量的、保守的标记/清除收集器。
Reference counting involves keeping a count of how many references to a given object are extant, then deleting the object automatically after the last one is released.
引用计数(reference counting)是对一个给定的对象当前有多少指向它的引用保留有一个计数，然后当最后一个引用被释放时自动删除该对象。
Reference counting is simple, but requires significant assistance from the compiler and imposes overhead on the mutator (the term for the user program, from the perspective of the garbage collector).
引用计数很简单，但是需要编译器的重要配合，并且增加了赋值函数(mutator)的开销(这个术语是针对用户程序的，是从垃圾收集器的角度来看的)。
Also, built-in functions and third-party libraries will not know about or be able to use your reference-counting mechanism.
另外，内置函数和第三方的库不会知道或者可以使用您的引用计数机制。
UMDF uses a reference-counting scheme to manage the lifetime of callback objects and framework objects.
UMDF使用引用计数方案来管理回调对象和框架对象的寿命。
UMDF uses a reference-counting scheme to manage the lifetime of callback objects and framework objects.
UMDF使用引用计数方案来管理回调对象和框架对象的寿命。
应用推荐