|
home—info—exams—lectures—labs—hws
Recipe—Laws—lies—syntax—java.lang docs—java.util docs
In our previous example for slicesReadyMsg, we handled zero as the same as any other plural. That was fine for a first attempt, but can we separately handle all three categories of 0, 1, and “more”, using just the syntax for if-else?
if (condition) { statements… } else { statements… } |
String slicesReadyMsg( String topping, int slicesReady ) { if (slicesReady == 1) { return "There is " + slicesReady + " piping hot slice of " + topping + " pizza, ready to eat!"; } else { // slicesReady isn't equal to 1 if (slicesReady ==0) { return "We are momentarily out of " + topping + " pizzas."; } else { return "There are " + slicesReady + " piping hot slices of " + topping + " pizza, ready to eat!"; } } } |
This idea of nesting an if-else statment inside another else clause is actually very common; it happens whenever we need to choose between more than two equal options. While what we wrote makes sense, it's annoying for two reasons:
/** Return a greeting, selected randomly from a list of several greetings. * @return A greeting (randomly selected, not necessarily uniformly). */ String greet() { int choice = (new java.util.Random()).nextInt(100); // We'll discuss the "new" statement later1; here's the upshot: the local variable // 'choice' now stores a number in the interval [0,99], a.k.a. [0,100). if (choice < 30) { return "Hello."; } else if (choice < 33) { return "Aloha."; } else if (choice < 50) { return "Buenos dias, amigo/amiga."; } else if (choice < 99) { return "Yo."; } else if (choice < 100) { // Not an advisable greeting. Use sparingly. return "I am a javabot: System dot out dot println open \"hello\" close."; } else { System.err.println( "This statement is unreachable (I hope)." ); return "A dummy return-statement to satisfy the compiler"; } // Is this line ever reached? Why or why not? } |
guideline: If your last condition is easy to phrase (as it is here), then certainly include it, making the last else unreachable. But don't bend over backwards, to do this; sometimes formulating that final condition is more error-prone than the savings you'd get!Mention: Arguably, it is bad to have more than one return in a method; (rather than always reaching the end of the method and returning a value there, for everybody to easily see). I don't insist on this, but you may have later teachers who do.
/** Given how many slices of (say) mushroom pizza are * currently available, create a nice tempting message * to advertise (shout out, or post, or put on a * LED sign...) * * @param topping The type of pizza (e.g. "pepperoni") * @param piecesReady The number of currently ready-to-serve * slices with the given topping. * @return A complete sentence describing the inventory. * For example: * inventoryMessage( "mushroom", 3 ) * = "There are 3 piping hot pieces of mushroom pizza, ready to eat!" */ String slicesReadyMsg( String topping, int slicesReady ) { String verbForm = "are"; // The correct verb for our result. String plurality = "s"; // The noun-suffix, correctly plural or singular. if (numInStock == 1) { verbForm = "is"; plurality = ""; } return "There " + verbForm + " " + slicesReady + + " piping hot slices of " + topping + ("pizza" + plurality) + " in stock."; } |
optional: The following explanation is optional, and will be skipped in lecture, as long as you read the concluding edict below.)Alas, omitting the brackets is bad for several reasons:
if (numInStock == 1) verbForm = "is"; else verbForm = "are"; |
if (numInStock == 1) verbForm = "is"; plurality = ""; // DANGER, WILL ROBINSON! else verbForm = "are"; plurality = "s"; |
Well, new is nothing too magical; it creates a particular instance of a class. In this case, the class isn't “PizzaServer” but “java.util.Random” (a longwinded name, indeed). And instances of this class can't be asked about pizzaArea, but they do know how to generate a nextInt randomly.
So far we have been making new instances in BlueJ by right-clicking on “new PizzaServer()” (or whatever our class is named), but “new” is actual Java code to do the same thing. Note that we could have even named this java.util.Random instance with a local variable, if we had wanted to:
java.util.Random ro = new java.util.Random(); int choice = ro.nextInt(100); |
2 So we could conceivably use a series of if statements (without else), rather than a big if-else. The second if statement is only reached when the first condition wasn't true (because in that case we'd return before ever reaching the second if condition). ↩
3So really, the actual syntax for Java's if-else statement is
if (statement) expression else expression |
home—info—exams—lectures—labs—hws
Recipe—Laws—lies—syntax—java.lang docs—java.util docs
©2008, Ian Barland, Radford University Last modified 2008.Feb.05 (Tue) |
Please mail any suggestions (incl. typos, broken links) to ibarlandradford.edu |