<--- Back to Details
First PageDocument Content
Computer programming / Data types / Method / Object-oriented programming / Automatic memory management / Finalizer / Weak reference / Destructor / Keepalive / Computing / Software engineering / Memory management
Date: 2014-02-06 19:37:32
Computer programming
Data types
Method
Object-oriented programming
Automatic memory management
Finalizer
Weak reference
Destructor
Keepalive
Computing
Software engineering
Memory management

Finalization should not be based on reachability Hans-J. Boehm HP Labs (This benefited from discussions with Mike Spertus and others.)

Add to Reading List

Source URL: hboehm.info

Download Document from Source Website

File Size: 267,37 KB

Share Document on Facebook

Similar Documents

Software engineering / Computing / Memory management / Computer programming / Finalizer / Finalization / Garbage collection / Manual memory management / Resource management / Resource Acquisition Is Initialization / Reference counting / Garbage

Adding Reference Counting to the Shared Source Common Language Infrastructure _Chris_Sells_ and _Christopher_Tavares_, Abstract Moving to a garbage-collected environment in the Common Language Runtime has, for th

DocID: 1pU1s - View Document

Destructors, Finalizers, and Synchronization Hans-J. Boehm HP Laboratories

Destructors, Finalizers, and Synchronization Hans-J. Boehm HP Laboratories

DocID: 1m2f7 - View Document

Software-Architecture Recovery from Machine Code∗ Venkatesh Karthik Srinivasan Thomas Reps  University of Wisconsin

Software-Architecture Recovery from Machine Code∗ Venkatesh Karthik Srinivasan Thomas Reps University of Wisconsin

DocID: 1lH2O - View Document

Finalizers, Threads, and the Java Memory Model Hans-J. Boehm HP Labs © 2004 Hewlett-Packard Development Company, L.P.

Finalizers, Threads, and the Java Memory Model Hans-J. Boehm HP Labs © 2004 Hewlett-Packard Development Company, L.P.

DocID: 1kH0Y - View Document

PDF Document

DocID: 1jbFr - View Document