There might be leaks, dangling Pointers, or incorrect memory usage.
可能是泄漏、空指针或者错误的内存使用。
In particular, the class itself has no way to avoid dangling Pointers.
尤其是，类本身无法避免悬垂指针。
Dangling Pointers are likely to arise in code, which USES memory in subtle ways.
悬空指针可能发生在以微妙方式使用内存的代码中。
There are two major memory-management hazards to avoid in non-garbage-collected languages: memory leaks and dangling Pointers.
在非垃圾收集语言中需要避免两个主要的内存管理危险：内存泄漏和悬空指针。
Unlike native environments, you are not responsible for memory leaks, dangling Pointers, uninitialized Pointers, or a host of other memory-management issues.
与原始环境不同，你不需要为内存泄漏、不定的指针、未初始化的指针或者其它内存管理陷阱问题负责。
To avoid dangling Pointers (the dangerous situation where a block of memory is freed but a pointer still references it), you must delete the object only after the last reference is released.
为了避免悬空指针(一种危险的情况，即一块内存已经被释放了，而一个指针还在引用它)，必须在最后的引用释放之后才删除对象。
To avoid dangling Pointers (the dangerous situation where a block of memory is freed but a pointer still references it), you must delete the object only after the last reference is released.
为了避免悬空指针(一种危险的情况，即一块内存已经被释放了，而一个指针还在引用它)，必须在最后的引用释放之后才删除对象。
应用推荐