This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

// Create a new Car object on

// the managed heap. We are

// returned a reference to this

// object ("refToMyCar").

Car refToMyCar = new Car("Zippy", 50);

// The C# dot operator (.) is used

// to invoke members on the object

// using our reference variable.

Console.WriteLine(refToMyCar.ToString());

Console.ReadLine();

}

}

Figure 8-1 illustrates the class, object, and reference relationship.

Figure 8-1.

References to objects on the managed heap

The Basics of Object Lifetime

When you are building your C# applications, you are correct to assume that the managed heap will

take care of itself without your direct intervention. In fact, the golden rule of .NET memory manage-

ment is simple:

■

Rule

Allocate an object onto the managed heap using the 

new

keyword and forget about it.

Once instantiated, the garbage collector will destroy the object when it is no longer needed.

The next obvious question, of course, is, “How does the garbage collector determine when an object

is no longer needed?” The short (i.e., incomplete) answer is that the garbage collector removes an

object from the heap when it is 

unreachable by any part of your code base. Assume you have a

method in your Program class that allocates a local Car object:

C H A P T E R   8  

■

U N D E R S TA N D I N G   O B J E C T   L I F E T I M E

246

8849CH08.qxd  10/22/07  1:27 PM  Page 246

---

static void MakeACar()

{