[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ProgSoc] Deterministic destruction of objects in garbage-collected languages



A FAQ [1,2] may be useful for those who don't know what the hell is
being said. It outlines the issues which may arise when an object
provides a finaliser method to be run manually or when the object is
garbage collected. A number of these issues are:

  * When can an object actually be finalised? This is trickier than it 
    first appears in the presence of some normally-desirable optimising 
    transformations.
  * In what thread, resource, or security context does a finalisation 
    function run?
  * What happens when registered objects reference each other?
  * What happens if a finalisation function makes an object not be 
    garbage any more?

See also the section specifically related to finalisation and
destruction [2].


Cheers,

--
Nathan de Vries

[1] http://www.iecc.com/gclist/GC-faq.html
[1] http://www.iecc.com/gclist/GC-lang.html

Attachment: smime.p7s
Description: S/MIME cryptographic signature