Section 4.2
Static Subroutines and Static Variables
EVERY SUBROUTINE IN JAVA MUST BE DEFINED
inside some class. This makes Java rather unusual among programming
languages, since most languages allow free-floating, independent
subroutines. One purpose of a class is to group together
related subroutines and variables. Perhaps the designers of
Java felt that everything must be related to something.
As a less philosophical motivation, Java's designers wanted
to place firm controls on the ways things are named, since
a Java program potentially has access to a huge number of
subroutines scattered all over the Internet. The fact that those
subroutines are grouped into named classes (and
classes are grouped into named "packages")
helps control the confusion that might result from so many
different names.
A subroutine that is a member of a class is
often called a method, and "method"
is the term that most people prefer for subroutines in Java. I will start using
the term "method" occasionally; however,
I will continue to prefer the term "subroutine" for static
subroutines. I will use the term "method" most often to refer
to non-static subroutines, which belong to objects rather than to
classes. This chapter will deal with static subroutines almost exclusively.
We'll turn to non-static methods and object-oriented programming in
the next chapter.
A subroutine definition in Java takes the form:
modifiers return-type subroutine-name ( parameter-list ) {
statements
}
It will take us a while -- most of the chapter -- to get through what all this means in detail.
Of course, you've already seen examples of subroutines in previous chapters, such as
the main() routine of a program and the paint() routine of an applet.
So you are familiar with the general format.
The statements between the braces, { and },
make up the body of the subroutine. These statements are
the inside, or implementation part, of the "black box", as discussed in the
previous section. They are the instructions
that the computer executes when the method is called. Subroutines can
contain any of the statements discussed in Chapter 2
and Chapter 3.
The modifiers that can occur at the beginning of
a subroutine definition are words that set certain characteristics of the method, such as whether
it is static or not. The modifiers that you've seen so far are "static"
and "public". There are only about a half-dozen possible modifiers altogether.
If the subroutine is a function, whose job is to compute some value,
then the return-type
is used to specify the type of value that is returned by the function. We'll be looking
at functions and return types in some detail in Section 4.
If the subroutine is not a function, then the return-type
is replaced by the special value void, which indicates that no value is returned.
The term "void" is meant to indicate that the return value is empty or non-existent.
Finally, we come to the parameter-list
of the method. Parameters are part of the interface of a subroutine.
They represent information that is passed into the subroutine from outside,
to be used by the subroutine's internal computations. For a concrete
example, imagine a class named Television that includes
a method named changeChannel(). The immediate question is:
What channel should it change to? A parameter can be used to answer
this question. Since the channel number is an integer, the type
of the parameter would be int, and the declaration of the
changeChannel() method might look like
public void changeChannel(int channelNum) {...}
This declaration specifies that changeChannel() has
a parameter named channelNum of type int. However,
channelNum does not yet have any particular value.
A value for channelNum is provided when the subroutine
is called; for example: changeChannel(17);
The parameter list in a subroutine can be empty, or it can consist of one or
more parameter declarations of the form
type parameter-name.
If there are several declarations, they are separated by commas. Note that each
declaration can name only one parameter. For example, if you want two parameters
of type double, you have to say "double x, double y",
rather than "double x, y".
Parameters are covered in more detail in the next section.
Here are a few examples of subroutine definitions, leaving out the statements that
define what the subroutines do:
public static void playGame() {
// "public" and "static" are modifiers; "void" is the
// return-type; "playGame" is the subroutine-name;
// the parameter-list is empty
. . . // statements that define what playGame does go here
}
int getNextN(int N) {
// there are no modifiers; "int" in the return-type
// "getNextN" is the subroutine-name; the parameter-list
// includes one parameter whose name is "N" and whose
// type is "int"
. . . // statements that define what getNextN does go here
}
static boolean lessThan(double x, double y) {
// "static" is a modifier; "boolean" is the
// return-type; "lessThan" is the subroutine-name; the
// parameter-list includes two parameters whose names are
// "x" and "y", and the type of each of these parameters
// is "double"
. . . // statements that define what lessThan does go here
}
In the second example given here, getNextN, is a non-static method,
since its definition does not include the modifier "static"
-- and so it's not an example that we should be looking at in this chapter!
The other modifier shown in the examples is "public".
This modifier indicates that the method can be called from anywhere
in a program, even from outside the class where the method is defined.
There is another modifier, "private", which indicates that the
method can be called only from inside the same class.
The modifiers public and private are called
access specifiers. If no
access specifier is given for a method, then by default, that method can
be called from anywhere in the "package" that contains the
class, but not from outside that package. (Packages were mentioned in
Section 3.7, and you'll learn more
about packages in this chapter, in
Section 5.) There is one other access modifier, protected,
which will only become relevant when we turn to object-oriented programming in
Chapter 5.
Note, by the way, that the main() routine of a program
follows the usual syntax rules for a subroutine. In
public static void main(String[] args) { .... }
the modifiers are public and static, the
return type is void, the subroutine name is main,
and the parameter list is "String[] args".
The only question might be about "String[]",
which has to be a type if it is to match the format of a parameter list.
In fact, String[] represents a so-called "array type",
so the syntax is valid. We will cover arrays in
Chapter 8. (The parameter, args,
represents information provided to the program when the main()
routine is called by the system. In case you know the term, the information
consists of any "command-line arguments" specified in
the command that the user typed to run the program.)
You've already had some experience with filling in the statements of
a subroutine. In this chapter, you'll learn all about writing your
own complete subroutine definitions, including the interface part.
When you define a subroutine, all you are doing is telling the computer
that the subroutine exists and what it does. The subroutine doesn't
actually get executed until it is called. (This is true even for
the main() routine in a class -- even though you don't call
it, it is called by the system when the system runs your program.)
For example, the playGame() method defined above could be
called using the following subroutine call statement:
playGame();
This statement could occur anywhere in the same class that includes
the definition of playGame(), whether in a main()
method or in some other subroutine. Since playGame() is a
public method, it can also be called from other classes,
but in that case, you have to tell the computer which class it
comes from. Let's say, for example, that playGame()
is defined in a class named Poker. Then to call playGame()
from outside the Poker class, you would have to say
Poker.playGame();
The use of the class name here tells the computer which class to look in
to find the method. It also lets you distinguish between Poker.playGame()
and other potential playGame() methods defined in other
classes, such as Roulette.playGame() or Blackjack.playGame().
More generally, a subroutine call statement takes the form
subroutine-name(parameters);
if the subroutine that is being called is in the same class, or
class-name.subroutine-name(parameters);
if the subroutine is a static subroutine defined elsewhere, in a different
class. (Non-static methods belong to objects rather than classes, and they
are called using object names instead of class names. More on that later.)
Note that the parameter list can be empty, as in the playGame() example,
but the parentheses must be there even if there is nothing between them.
It's time to give an example of what a complete program looks
like, when it includes other subroutines in addition to the main() routine.
Let's write a program that plays a guessing game with the user. The computer
will choose a random number between 1 and 100, and the user will try to guess it.
The computer tells the user whether the guess is high or low or correct.
If the user gets the number after six guesses or fewer, the user wins the game.
After each game, the user has the option of continuing with another game.
Since playing one game can be thought of as a single, coherent task, it makes
sense to write a subroutine that will play one guessing game with the user.
The main() routine will use a loop to call the playGame() subroutine
over and over, as many times as the user wants to play. We approach the problem of
designing the playGame() subroutine the same way we write a main() routine:
Start with an outline of the algorithm and apply stepwise refinement. Here is a
short pseudocode algorithm for a guessing game program:
Pick a random number
while the game is not over:
Get the user's guess
Tell the user whether the guess is high, low, or correct.
The test for whether the game is over is complicated, since the game ends if
either the user makes a correct guess or the number of guesses is six.
As in many cases, the easiest thing to do is to use a
"while (true)" loop and use break to end the loop whenever
we find a reason to do so. Also,
if we are going to end the game after six guesses,
we'll have to keep track of the number of guesses that the user has made.
Filling out the algorithm gives:
Let computersNumber be a random number between 1 and 100
Let guessCount = 0
while (true):
Get the user's guess
Count the guess by adding 1 to guess count
if the user's guess equals computersNumber:
Tell the user he won
break out of the loop
if the number of guesses is 6:
Tell the user he lost
break out of the loop
if the user's guess is less than computersNumber:
Tell the user the guess was low
else if the user's guess is higher than computersNumber:
Tell the user the guess was high
With variable declarations added and
translated into Java, this becomes the definition of the playGame() routine.
A random integer between 1 and 100 can be computed as (int)(100 * Math.random()) + 1.
I've cleaned up the interaction with the user to make it flow better.
static void playGame() {
int computersNumber; // A random number picked by the computer.
int usersGuess; // A number entered by user as a guess.
int guessCount; // Number of guesses the user has made.
computersNumber = (int)(100 * Math.random()) + 1;
// The value assigned to computersNumber is a randomly
// chosen integer between 1 and 100, inclusive.
guessCount = 0;
TextIO.putln();
TextIO.put("What is your first guess? ");
while (true) {
usersGuess = TextIO.getInt(); // get the user's guess
guessCount++;
if (usersGuess == computersNumber) {
TextIO.putln("You got it in " + guessCount
+ " guesses! My number was " + computersNumber);
break; // the game is over; the user has won
}
if (guessCount == 6) {
TextIO.putln("You didn't get the number in 6 guesses.");
TextIO.putln("You lose. My number was " + computersNumber);
break; // the game is over; the user has lost
}
// If we get to this point, the game continues.
// Tell the user if the guess was too high or too low.
if (usersGuess < computersNumber)
TextIO.put("That's too low. Try again: ");
else if (usersGuess > computersNumber)
TextIO.put("That's too high. Try again: ");
}
TextIO.putln();
} // end of playGame()
Now, where exactly should you put this? It should be part of the same class as the
main() routine, but not inside the main routine. It is not legal to have one
subroutine physically nested inside another. The main() routine will call
playGame(), but not contain it physically. You can put the definition of
playGame() either before or after the main() routine. Java is not
very picky about having the members of a class in any particular order.
It's pretty easy to write the main routine. You've done things like this before.
Here's what the complete program looks like (except that a serious program
needs more comments than I've included here).
public class GuessingGame {
public static void main(String[] args) {
TextIO.putln("Let's play a game. I'll pick a number between");
TextIO.putln("1 and 100, and you try to guess it.");
boolean playAgain;
do {
playGame(); // call subroutine to play one game
TextIO.put("Would you like to play again? ");
playAgain = TextIO.getlnBoolean();
} while (playAgain);
TextIO.putln("Thanks for playing. Goodbye.");
} // end of main()
static void playGame() {
int computersNumber; // A random number picked by the computer.
int usersGuess; // A number entered by user as a guess.
int guessCount; // Number of guesses the user has made.
computersNumber = (int)(100 * Math.random()) + 1;
// The value assigned to computersNumber is a randomly
// chosen integer between 1 and 100, inclusive.
guessCount = 0;
TextIO.putln();
TextIO.put("What is your first guess? ");
while (true) {
usersGuess = TextIO.getInt(); // get the user's guess
guessCount++;
if (usersGuess == computersNumber) {
TextIO.putln("You got it in " + guessCount
+ " guesses! My number was " + computersNumber);
break; // the game is over; the user has won
}
if (guessCount == 6) {
TextIO.putln("You didn't get the number in 6 guesses.");
TextIO.putln("You lose. My number was " + computersNumber);
break; // the game is over; the user has lost
}
// If we get to this point, the game continues.
// Tell the user if the guess was too high or too low.
if (usersGuess < computersNumber)
TextIO.put("That's too low. Try again: ");
else if (usersGuess > computersNumber)
TextIO.put("That's too high. Try again: ");
}
TextIO.putln();
} // end of playGame()
} // end of class GuessingGame
Take some time to read the program carefully and figure out how it works.
And try to convince yourself that even in this relatively simple case,
breaking up the program into two methods makes the program easier to understand
and probably made it easier to write each piece.
You can try out a simulation of this program here:
A class can include other things besides subroutines. In particular, it can
also include variable declarations. Of course, you can have variable declarations
inside subroutines. Those are called local variables.
However, you can also have variables that are not part of any subroutine. To distinguish
such variables from local variables, we call them member
variables, since they are members of a class.
Just as with subroutines, member variables can be either static or non-static. In this
chapter, we'll stick to static variables. A static member variable belongs to the
class itself, and it exists as long as the class exists. Memory is allocated for the
variable when the class is first loaded by the Java interpreter. Any assignment
statement that assigns a value to the variable changes the content of that memory,
no matter where that assignment statement is located in the program. Any time the
variable is used in an expression, the value is fetched from that same memory,
no matter where the expression is located in the program. This means that the
value of a static member variable can be set in one subroutine and used in
another subroutine. Static member variables are "shared" by all the
static subroutines in the class. A local variable in a subroutine, on the other hand,
exists only while that subroutine is being executed, and is completely inaccessible
from outside that one subroutine.
The declaration of a member variable looks just like the declaration of
a local variable except for two things: The member variable is declared outside
any subroutine (although it still has to be inside a class), and the
declaration can be marked with modifiers such as static,
public, and private. Since we are only working with static member variables
for now, every declaration of a member variable in this chapter will
include the modifier static. For example:
static int numberOfPlayers;
static String usersName;
static double velocity, time;
A static member variable that is not declared to be private can be
accessed from outside the class where it is defined, as well as inside. When
it is used in some other class, it must be referred to with a compound identifier
of the form class-name.variable-name.
For example, the System class contains the public static member variable named out,
and you use this variable in your own classes by referring to System.out. If
numberOfPlayers is a public static member variable in a class named
Poker, subroutines in the Poker class would refer to it simply as
numberOfPlayers. Subroutines in another class would refer to it as
Poker.numberOfPlayers.
As an example, let's add a static member variable to the GuessingGame
class that we wrote earlier in this section. This variable will be
used to keep track of how many games the user wins. We'll
call the variable gamesWon and declare it with the statement
"static int gamesWon;" In the playGame() routine,
we add 1 to gamesWon if the user wins the game. At the end of the main()
routine, we print out the value of gamesWon. It would be impossible
to do the same thing with a local variable, since we need access to the same variable from
both subroutines.
When you declare a local variable in a subroutine, you have to assign a value to
that variable before you can do anything with it. Member variables, on the other
hand are automatically initialized with a default value.
For numeric variables, the default value is zero.
For boolean variables, the default is false. And for
char variables, it's the unprintable character that has Unicode code
number zero. (For objects, such as Strings, the default initial
value is a special value called null, which we won't encounter officially
until later.)
Since it is of type int, the static member variable gamesWon
automatically gets assigned an initial
value of zero. This happens to be the correct initial value for a variable that
is being used as a counter. You can, of course, assign a different value
to the variable at the beginning of the main() routine if
you are not satisfied with the default initial value.
Here's a revised version of GuessingGame.java that includes
the gamesWon variable. The changes from
the above version are shown in red:
public class GuessingGame2 {
static int gamesWon; // The number of games won by
// the user.
public static void main(String[] args) {
gamesWon = 0; // This is actually redundant, since 0 is
// the default initial value.
TextIO.putln("Let's play a game. I'll pick a number between");
TextIO.putln("1 and 100, and you try to guess it.");
boolean playAgain;
do {
playGame(); // call subroutine to play one game
TextIO.put("Would you like to play again? ");
playAgain = TextIO.getlnBoolean();
} while (playAgain);
TextIO.putln();
TextIO.putln("You won " + gamesWon + " games.");
TextIO.putln("Thanks for playing. Goodbye.");
} // end of main()
static void playGame() {
int computersNumber; // A random number picked by the computer.
int usersGuess; // A number entered by user as a guess.
int guessCount; // Number of guesses the user has made.
computersNumber = (int)(100 * Math.random()) + 1;
// The value assigned to computersNumber is a randomly
// chosen integer between 1 and 100, inclusive.
guessCount = 0;
TextIO.putln();
TextIO.put("What is your first guess? ");
while (true) {
usersGuess = TextIO.getInt(); // get the user's guess
guessCount++;
if (usersGuess == computersNumber) {
TextIO.putln("You got it in " + guessCount
+ " guesses! My number was " + computersNumber);
gamesWon++; // Count this game by incrementing gamesWon.
break; // the game is over; the user has won
}
if (guessCount == 6) {
TextIO.putln("You didn't get the number in 6 guesses.");
TextIO.putln("You lose. My number was " + computersNumber);
break; // the game is over; the user has lost
}
// If we get to this point, the game continues.
// Tell the user if the guess was too high or too low.
if (usersGuess < computersNumber)
TextIO.put("That's too low. Try again: ");
else if (usersGuess > computersNumber)
TextIO.put("That's too high. Try again: ");
}
TextIO.putln();
} // end of playGame()
} // end of class GuessingGame2
