AhmadLang / Java, How To Program, 2004

getCount (lines 4649). The static variable count is initialized to zero in line 9. If a static variable is not initialized, the compiler assigns a default value to the variablein this case 0, the default value for type int. Variable count maintains a count of the number of objects of class Employee that currently reside in memory. This includes objects that have already been marked for garbage collection by the JVM, but have not yet been reclaimed by the garbage collector.

Figure 8.12. static variable used to maintain a count of the number of Employee objects in memory.

(This item is displayed on pages 381 - 382 in the print version)

5public class Employee

6{

7private String firstName;

8private String lastName;

9 private static int count = 0; // number of objects in memory 10

11// initialize employee, add 1 to static count and

12// output String indicating that constructor was called

13public Employee( String first, String last )

14{

15firstName = first;

16lastName = last;

17

18count++; // increment static count of employees

19System.out.printf( "Employee constructor: %s %s; count = %d\n",

20firstName, lastName, count );

21} // end Employee constructor

22

23// subtract 1 from static count when garbage

24// collector calls finalize to clean up object;

25// confirm that finalize was called

26protected void finalize()

27{

28count--; // decrement static count of employees

29System.out.printf( "Employee finalizer: %s %s; count = %d\n",

30firstName, lastName, count );

31} // end method finalize

32

33// get first name

34public String getFirstName()

35{

36return firstName;

37} // end method getFirstName

39// get last name

40public String getLastName()

41{

42return lastName;

43} // end method getLastName

45// static method to get static count value

46public static int getCount()

47{

48return count;

49} // end method getCount

50} // end class Employee

Figure 8.13. static member demonstration.

(This item is displayed on pages 382 - 383 in the print version)

1 // Fig. 8.13: EmployeeTest.java

2 // Static member demonstration.

3

4public class EmployeeTest

5{

6 public static void main( String args[] )

7{

8// show that count is 0 before creating Employees

9System.out.printf( "Employees before instantiation: %d\n",

10Employee.getCount() );

11

12// create two Employees; count should be 2

13Employee e1 = new Employee( "Susan", "Baker" );

14Employee e2 = new Employee( "Bob", "Blue" );

15

16// show that count is 2 after creating two Employees

17System.out.println( "\nEmployees after instantiation: " );

18System.out.printf( "via e1.getCount(): %d\n", e1.getCount() );

19System.out.printf( "via e2.getCount(): %d\n", e1.getCount() );

20System.out.printf( "via Employee.getCount(): %d\n",

21Employee.getCount() );

22

23// get names of Employees

24System.out.printf( "\nEmployee 1: %s %s\nEmployee 2: %s %s\n\n",

25e1.getFirstName(), e1.getLastName(),

26e2.getFirstName(), e2.getLastName() );

31e1 = null;

32e2 = null;

34System.gc(); // ask for garbage collection to occur now

36// show Employee count after calling garbage collector; count

37 // displayed may be 0, 1 or 2 based on whether garbage collector

38// executes immediately and number of Employee objects collected

39System.out.printf( "\nEmployees after System.gc(): %d\n",

40Employee.getCount() );

41} // end main

42} // end class EmployeeTest

Employees before instantiation: 0

Employee constructor: Susan Baker; count = 1

Employee constructor: Bob Blue; count = 2

Employees after instantiation: via e1.getCount(): 2

via e2.getCount(): 2

via Employee.getCount(): 2

Employee 1: Susan Baker

Employee 2: Bob Blue

Employee finalizer: Bob Blue; count = 1

Employee finalizer: Susan Baker; count = 0

Employees after System.gc(): 0

When Employee objects exist, member count can be used in any method of an Employee objectthis example increments count in the constructor (line 18) and decrements it in the finalize method (line 28). When no objects of class Employee exist, member count can still be referenced, but only through a call to public static method getCount (lines 4649), as in Employee.getCount(), which returns the number of Employee objects currently in memory. When objects exist, method getCount can also be

called through any reference to an Employee object, as in the call e1.getCount().

[Page 383]

Good Programming Practice 8.1

Invoke every static method by using the class name and a dot (.) to emphasize that the method being called is a static method.

[Page 384]

Note that the Employee class has a finalize method (lines 2631). This method is included only to show when the garbage collector executes in this program. Method finalize is normally declared protected, so it is not part of the public services of a class. We will discuss the protected member access modifier in detail in Chapter 9.

EmployeeTest method main (Fig. 8.13) instantiates two Employee objects (lines 1314). When each Employee object's constructor is invoked, lines 1516 of Fig. 8.12 assign the Employee's first name and last name to instance variables firstName and lastName. Note that these two statements do not make copies of the original String arguments. Actually, String objects in Java are immutablethey cannot be modified after they are created. Therefore, it is safe to have many references to one String object. This is not normally the case for objects of most other classes in Java. If String objects are immutable, you might wonder why are we able to use operators + and += to concatenate String objects. String concatenation operations actually result in a new Strings object containing the concatenated values. The original String objects are not modified.

When main has finished using the two Employee objects, the references e1 and e2 are set to null at lines 3132. At this point, references e1 and e2 no longer refer to the objects that were instantiated on lines 1314. This "marks the objects for garbage collection" because there are no more references to the objects in the program.

Eventually, the garbage collector might reclaim the memory for these objects (or the operating system surely will reclaim the memory when the program terminates). The JVM does not guarantee when the garbage collector will execute (or even whether it will execute), so this program explicitly calls the garbage collector in line 34 using static method gc of class System (package java.lang) to indicate that the garbage collector should make a best-effort attempt to reclaim objects that are eligible for garbage collection. This is just a best effortit is possible that no objects or only a subset of the eligible objects will be collected. In Fig. 8.13's sample output, the garbage collector did execute before lines 3940 displayed current Employee count. The last output line indicates that the number of Employee objects in memory is 0 after the call to System.gc(). The thirdand second-to-last lines of the output show that the Employee object for Bob Blue was finalized before the Employee object for Susan Baker. The output on your system may differ, because the garbage collector is not guaranteed to execute when System.gc() is called, nor is it guaranteed to collect objects in a specific order.

[Note: A method declared static cannot access non-static class members, because a static method can be called even when no objects of the class have been instantiated. For the same reason, the this reference cannot be used in a static methodthe this reference must refer to a specific object of the class, and when a static method is called, there might not be any objects of its class in memory. The this reference is required to allow a method of a class to access other non-static members of the same class.]

Common Programming Error 8.7

A compilation error occurs if a static method calls an instance (non-static) method in the same class by using only the method name. Similarly, a compilation error occurs if a static method attempts to access an instance variable in the same class by using only the variable name.

Common Programming Error 8.8

Referring to this in a static method is a syntax error.

[Page 385]

8.12. static Import

In Section 6.3, you learned about the static fields and methods of class Math. We invoked class Math's static fields and methods by preceding each with the class name Math and a dot (.). A static import declaration (a new feature of J2SE 5.0) enables programmers to refer to imported static members as if they were declared in the class that uses themthe class name and a dot (.) are not required to use an imported static member.

A static import declaration has two formsone that imports a particular static member (which is known as single static import) and one that imports all static members of a class (which is known as

static import on demand). The following syntax imports a particular static member:

import static packageName.ClassName.staticMemberName;

where packageName is the package of the class (e.g., java.lang), ClassName is the name of the class (e.g., Math) and staticMemberName is the name of the static field or method (e.g., PI or abs). The following syntax imports all static members of a class:

import static packageName.ClassName.*;

where packageName is the package of the class (e.g., java.lang) and ClassName is the name of the class (e.g., Math). The asterisk (*) indicates that all static members of the specified class should be available for use in the class(es) declared in the file. Note that static import declarations import only static class members. Regular import statements should be used to specify the classes used in a program.

Figure 8.14 demonstrates a static import. Line 3 is a static import declaration, that imports all static fields and methods of class Math from package java.lang. Lines 912 access the Math class's static field E (line 11) and the static methods sqrt (line 9), ceil (line 10), log (line 11) and cos (line 12) without preceding the field name or method names with class name Math and a dot.

Figure 8.14. Static import Math methods.

5public class StaticImportTest

6{

7public static void main( String args[] )

8{

9System.out.printf( "sqrt( 900.0 ) = %.1f\n", sqrt( 900.0 ) );

13} // end main

14} // end class StaticImportTest

sqrt( 900.0 ) = 30.0 ceil( -9.8 ) = -9.0 log( E ) = 1.0

cos( 0.0 ) = 1.0

[Page 386]

Common Programming Error 8.9

A compilation error occurs if a program attempts to import static methods that have the same signature or static fields that have the same name from two or more classes.

Attempts to modify a final instance variable are caught at compilation time rather than causing execution-time errors. It is always preferable to get bugs out at compilation time, if possible, rather than allow them to slip through to execution time (where studies have found that the cost of repair is often many times more expensive).

[Page 388]

Software Engineering Observation 8.14

A final field should also be declared static if it is initialized in its declaration. Once a final field is initialized in its declaration, its value can never change. Therefore, it is not necessary to have a separate copy of the field for every object of the class. Making the field static enables all objects of the class to share the final field.

If a final variable is not initialized, a compilation error occurs. To demonstrate this, we placed line 12 of Fig. 8.15 in a comment and recompiled the class. Fig. 8.17 shows the error message produced by the compiler.

Figure 8.17. final variable INCREMENT must be initialized.

Increment.java:13: variable INCREMENT might not have been initialized } // end Increment constructor

^

1 error

Common Programming Error 8.11

Not initializing a final instance variable in its declaration or in every constructor of the class yields a compilation error indicating that the variable might not have been initialized. The same error occurs if the class initializes the variable in some, but not all, of the class's constructors.