<< Chapter < Page Chapter >> Page >

This case violates the rule

In this case, the method named m is defined in the class named B , which is two levels down from the class named Object .

The method named m is neither defined in nor inherited into the class named Object .

When the reference to the object of the class B was assigned to the reference variable of type Object , the type of the reference was automatically converted to type Object .

Therefore, because the reference is type Object , it cannot be used directly to call the method named m .

The solution is a downcast

In this case, the solution to the problem is a downcast.

The code in Listing 6 shows an attempt to solve the problem by casting the reference down the hierarchy to type A .

Listing 6 . Try a downcast to type A.

//Following will not compile //((A)var).m();

Still doesn't solve the problem

However, this still doesn't solve the problem, and the result is another compiler error.

The method named m is neither defined in nor inherited into the class named A .

Again, it was necessary to convert the statement into a comment in order to cause the program to compile.

What is the problem here?

The problem with this approach is that the downcast simply didn't go far enough down the inheritance hierarchy.

The class named A does not contain a definition of the method named m . Neither does it inherit the method named m . The method named m is defined in class B, which is a subclass of A .

Therefore, a reference of type A is no more useful than a reference of type Object insofar as calling the method named m is concerned.

The real solution

The solution to the problem is shown in Listing 7 .

Listing 7 . Try a downcast to type B.

//Following will compile and run ((B)var).m();

The code in Listing 7 casts (temporarily converts) the reference value contained in the Object variable named var to type B .

The method named m is defined in the class named B . Therefore, a reference of type B can be used to call the method.

The code in Listing 7 compiles and executes successfully. This causes the method named m to execute, producing the following output on the computer screen:

m in class B

A few odds and ends

Before leaving this topic, let's look at a few more issues.

The code in Listing 8 declares and populates a new variable of type B.

Listing 8 . Assign var to v1.

//Following will compile and run B v1 = (B)var;

The code in Listing 8 uses a cast to:

  • Convert the contents of the Object variable to type B
  • Assign the converted reference to the new reference variable of type B .

This is a legal operation. In this class hierarchy, the reference to the object of the class B can be assigned to a reference variable of the types B, A , or Object .

While this operation is legal, it is usually not a good idea to have two different reference variables that contain references to the same object. Inthis case, the variables named var and v1 both contain a reference to the same object.

Cannot be assigned to type C

However, the reference to the object of the class B cannot be assigned to a reference variable of any other type, including type C . An attempt to do so is shown in Listing 9 .

Get Jobilize Job Search Mobile App in your pocket Now!

Get it on Google Play Download on the App Store Now




Source:  OpenStax, Xna game studio. OpenStax CNX. Feb 28, 2014 Download for free at https://legacy.cnx.org/content/col11634/1.6
Google Play and the Google Play logo are trademarks of Google Inc.

Notification Switch

Would you like to follow the 'Xna game studio' conversation and receive update notifications?

Ask