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

// Make a Point by setting each property manually...

Point firstPoint = new Point();

C H A P T E R   1 3  

■

C #   2 0 0 8   L A N G U A G E   F E AT U R E S

436

8849CH13.qxd  10/2/07  12:42 PM  Page 436

---

firstPoint.X = 10;

firstPoint.Y = 10;

// ...or make a Point via a custom constructor...

Point anotherPoint = new Point(20, 20);

// ...or make some Point types using the new object init syntax.

var yetAnotherPoint = new Point { X = 30, Y = 30 };

Point finalPoint = new Point { X = 30, Y = 30 };

Console.ReadLine();

}

The final two Point types (one of which is implicitly typed, just for the purpose of illustration)

are not making use of a custom type constructor (as one might do traditionally), but are rather set-

ting values to the public X and Y properties. Behind the scenes, the type’s default constructor is

invoked, followed by setting the values to the specified properties. To this end, yetAnotherPoint and

finalPoint are just shorthand notations for the syntax used to create the firstPoint variable (going

property by property).

Now recall that this same syntax can be used to set public fields of a type, which Point cur-

rently does not support. However, for the sake of argument, assume that the xPos and yPos member

variables have been declared publicly. We could now set values to these fields as follows:

var p = new Point {xPos = 2, yPos = 3};

Given that Point now has four public members, the following syntax is also legal. However, try

to figure out the actual final values of xPos and yPos:

var p = new Point {xPos = 2, yPos = 3, X = 900};

As you might guess, xPos is set to 900, while yPos is the value 3. From this, you can correctly

infer that object initialization is performed in a left-to-right manner. To clarify, the previous initial-

ization of p using standard object constructor syntax would appear as follows:

Point p = new Point();

p.xPos = 2;

p.yPos = 3;

p.X = 900;