Question

我不理解你为什么不改变同yn。如果有人提到某一物体,而该物体的范围并不大,则标明该物体为GC的物体,而不加以破坏。如果情况如此,它完全有理由加以破坏。

这是否是因为该类人本身的行为不同,而该物体是否参考了? Seems solvable - if Object has a destructor, its aprtime wrong for an instance to go out of scope if there are external reference.

Please help me understand.

Answer 1

因此,我可以理解的答案是,以这种方式执行ack物体是可行的,但需要一个计算垃圾收集器。 Java(大概为NET)避免了这条路,因为:

You can augment refcounting with a "real" GC, which naturally has to run less often because only some (often small) part of the garbage generated contains cycles. Another factor is speed - a clever, optimized GC can do much better than refcounting, in particular in the presence of threads (which make incrementing/decrementing the refcounts much more costy, due to locking)

见。

Answer 2

通常采用的通用公平市价会计核算制度不使用参照计算;因此,依赖参考计算的任何办法都不会依赖典型的国际交易日志。但是,如果提及联合核查机制,这种执行可能要慢得多。

It s not clear to me what approach you suggest in your posting. If you want somehow detect that a reference is made to an object, most likely, even the most trivial object usages would break your detection, e.g.

{
 A a = new A();
 a.m();
}

这有两个问题:

Reading the local variable a already makes a reference to the object (on the evaluation stack). If "making a reference" is already considered as "not eligible as a stack object", then the approach of stack objects would be impractical
A method is called on the object, which, in turn, might make a reference to this inside, invisible to the caller. So even if you have a policy that somehow allows access to local variables containing stack objects, you can t really allow method calls for stack objects. As that would include the call to finalize(), having stack object would be fairly pointless.

Answer 3

why you can t have stack objects without changing syntax. If anyone makes a reference to an object that doesn t go out of scope, flag the object for GC and don t destruct it.

除标的为,占用了您可能需要的下一个方法电话的空间。

Answer 4

我认为,这一要求是有问题的:

如果物体有脱轨器,如果有外部参考,则该物体的运行时间差错,无法进入场面。

because it means you would need to do a GC cycle on return from any method that declared a local variable whose type has a destructor.

哪些工作可能与以下几个类似:http://smarteiffel.loria.fr/wiki/en/index.php/Expanded_or_vis”rel=“nofollow”>expanded变量。从扩大的变量中划入参考变量(包括方法参数)是非法的,因此不能出现这一问题。

Answer 5

简单的答复是,GC isn t在每一物体的删除上运行――它定期运行――而且它为什么现在除了第7JDK之外,还在尝试资源之外作出努力。

http://blogs.oracle.com/darcy/enter/project_form_try_out_try

甚至在有GC框架的情况下,C++通过单独的概念处理RAII的问题。

友情链接