Why Java?

Subsection 2.3.1 First Java Program

Every program in Java is written as a class. Java is an object-oriented language and we’ll learn more about classes and objects in later chapters. Inside the class, there can be a main method that starts the program. When you ask the Java run-time to run a class, it will always start execution in the main method. Here is the template for a simple Java program with a main method:

🔗

public class MyClass
{
public static void main(String[] args)
{
// Put your code here!
}
}

Note 2.3.1.

In Java every open curly brace { must have a matched close curly brace }. These are used to start and end class definitions and method definitions.

🔗

Checkpoint 2.3.2.

Run this code to see the output below it. Then change the code to print your name, for example “Hi Pat!”, and run again.

🔗

During the lab, we will see how we run Java locally in an integrated development environment (IDE) on your computer. One important takeaway here is that all code (programs) in Java must be defined inside a class in a source file, and the name of the class must match the file name.

🔗

Subsection 2.3.2 Print Commands

Java has two different print commands to print output to the screen:

🔗

System.out.println(value) : prints the value followed by a new line (ln)
🔗

🔗
System.out.print(value) : prints the value without advancing to the next line
🔗

🔗

🔗

System.out.println("Hi there!"); prints out the characters between the first " and the second " followed by a new line. The "Hi there!" is called a string literal, and it can have zero to many characters enclosed in starting and ending double quotes.

🔗

Checkpoint 2.3.3.

Run this code to see the output below it. How would you change it to print the ! on the same line as Hi there keeping all 3 print statements?

🔗

Most command keywords in Java must be in lowercase, but class names such as System and String are capitalized. Commands in Java must end with a semicolon (;). Think of the semicolon (;) in Java like a period (.) in English. You use a semicolon (;) to show the end of a Java statement, just the way you use a period (.) to show the end of an English sentence.

🔗

Subsection 2.3.3 Syntax Errors and Debugging

Computers don’t actually speak Java so we have to compile (translate) Java source files that we write into class files which is code that a computer can understand and run. In this e-book, the Java code is actually being sent to a Java server to compile and run, and the output is sent back to show on the same page.

🔗

Syntax errors are reported to you by the compiler if your Java code is not correctly written. Examples of syntax errors are a semicolon ; missing or if the code has a open curly brace { or open quote ", but no close curly brace } or close quote ". Informally, a syntax error is called a bug, and the process of removing errors is called debugging. An early computer science pioneer Grace Hopper documented a real bug, a moth that flew into a computer in 1947!

🔗

Figure 2.3.4. Figure 2: Grace Hopper’s log showing a real bug, 1947.
🔗

The compiler tries to run your code, but if your code has syntax errors, you will see error messages displayed below the code. Compiler error messages will tell the line number that the compiler found the error and the type of error. The error messages are not always easy to understand and sometimes the actual error is before the line that the compiler says is the problem.

🔗

Watch the following video to see that all coders get bugs. Debugging is a normal part of coding. It can be frustrating at times, but you will get better at it with practice! Sometimes another pair of eyes really helps, so ask a friend if you get stuck or try explaining your code line by line to someone or even a rubber duck. Rubber duck debugging is a lot of fun!

🔗

Let’s practice debugging some code!

🔗

Check Your Understanding: Mixed up programs

🔗

Checkpoint 2.3.5.

The following has all the correct code to print out “Hi my friend!” when the code is run, but the code is mixed up. Drag the blocks from left to right and put them in the correct order. Click on the “Check Me” button to check your solution. You will be told if any of the blocks are in the wrong order or if you need to remove one or more blocks. After three incorrect attempts you will be able to use the Help Me button to make the problem easier.

🔗

public class ThirdClass
{
---
 public static void main(String[] args)
 {
 
---
 System.out.println("Hi my friend!");
 
---
 }
 
---
}

🔗

Checkpoint 2.3.6.

The following has all the correct code to print out “Hi there!” when the code is run, but the code is mixed up and contains some extra blocks with errors. Drag the needed blocks from left to right and put them in the correct order. Click on the “Check Me” button to check your solution.

🔗

public class FourthClass
{
---
public Class FourthClass
{  #paired
---
 public static void main(String[] args)
 {
 
---
 public static void main()
 { 
  #paired
---
 System.out.println("Hi there!");
 
---
 System.out.println("Hi there!") 
  #paired
---
 }
 
---
}

🔗

Coding Exercise: Compile Time Error 1

🔗

Click on the Run button below to try and run the following code. Look for an error message after the code. This is called a compile time error because it is an error detected by the compiler.

🔗

What is wrong? Can you fix it? The error message will tell you the line number that it thinks is causing the error (FirstClass.java:5: error: unclosed string literal). Check line 5 to make sure that everything looks correct. One good thing to check is that all { have a matching } and all ( have a matching ) and all starting " have a ending " as well. Try putting in the missing symbol and run again. This is called debugging.

🔗

Checkpoint 2.3.7.

Fix the code below.

🔗

Coding Exercise: Compile Time Error 2

🔗

Click on the Run button below to try and run the following code. Look for an error message after the code. What is wrong this time? Can you fix it? One good thing to check is that all { have a matching } and all ( have a matching ) and all starting " have a ending " as well.

🔗

Checkpoint 2.3.8.

Fix the code below.

🔗

Coding Exercise: Compile Time Error 3

🔗

Click on the Run button below to try and run the following code. What is wrong this time? Can you fix it? After you fix the first error, you may encounter a 2nd error! Fix that one too! Hints: How do you end a command in Java? Also, check for capitalization.

🔗

Checkpoint 2.3.9.

Fix the code below.

🔗

Did you remember that System is capitalized in System.out.println? Did you find the missing semicolon?

🔗

Subsection 2.3.4 Comments

In Java and many text-based coding languages, // is used to mark the beginning of a comment. For multi-line comments, use /* to start the comment and */ to end the comment. The compiler will skip over comments. However, it is a good idea to use comments to make notes to yourself and other programmers working with you. Here are some examples of good commenting:

🔗

/* MyClass.java
Programmer: My Name
Date:
*/

int max = 10; // this keeps track of the max score

🔗

Subsection 2.3.5 Summary

A basic Java program looks like the following:
🔗

🔗

🔗

public class MyClass
{
public static void main(String[] args)
{
System.out.println("Hi there!");
}
}

A Java program starts with public class NameOfClass { }. If you are using your own files for your code, each class should be in a separate file that matches the class name inside it, for example NameOfClass.java.
🔗

🔗
Most Java classes have a main method that will be run automatically. It looks like this: public static void main(String[] args) { }.
🔗

🔗
The System.out.print() and System.out.println() methods display information given inside the parentheses on the computer monitor.
🔗

🔗
System.out.println moves the cursor to a new line after the information has been displayed, while System.out.print does not.
🔗

🔗
A string literal is enclosed in double quotes (’’ ‘’).
🔗

🔗
Java command lines end in ; (semicolon). { } are used to enclose blocks of code. // and /* */ are used for comments.
🔗

🔗
A compiler translates Java code into a class file that can be run on your computer. Compiler or syntax errors are reported to you by the compiler if the Java code is not correctly written. Some things to check for are ; at end of command lines, matching { }, (), and “”.
🔗

🔗

🔗

Subsection 2.3.6 Practice

Checkpoint 2.3.10.

1-2-11: Consider the following code segment.

🔗

System.out.print("Java is ");
System.out.println("fun ");
System.out.print("and cool!");

What is printed as a result of executing the code segment?

🔗

```
Java is fun and cool!
```
Notice the println in line 2.
```
Java isfun
and cool!
```
Notice the space after is in the first line.
```
Java is
fun
and cool!
```
Notice that the first line is a print, not println.
```
Java is fun
and cool!
```
Correct! Pay attention to which lines are print or println.

🔗

Checkpoint 2.3.11.

1-2-12: Consider the following code segment.

🔗

System.out.println("Roses are red, ") // Line 1;
System.out.println("Violets are blue, ") // Line 2;
System.out.print("Unexpected '}' ") // Line 3;
System.out.print("on line 32. ") // Line 4;

The code segment is intended to produce the following output but may not work as intended.

🔗

Roses are red,
Violets are blue,
Unexpected '}' on line 32.

Which change, if any, can be made so that the code segment produces the intended output?

🔗

Replacing print with println on lines 3 and 4.
These should print on the same line without a newline in between.
Replacing println with print on lines 1 and 2.
These should print out with a newline in between.
Removing the single quotes in line 3.
The single quotes are fine in this line.
Putting the semicolon after the ) on each line.
Correct! The semicolon should go after each command but not in the comment.

🔗

ITSC 1213 - Introduction to CS 2 How to Design Programs with Object Oriented Programming

Section 2.3 Why Java?

Subsection 2.3.1 First Java Program

Note 2.3.1.

Checkpoint 2.3.2.

Subsection 2.3.2 Print Commands

Checkpoint 2.3.3.

Subsection 2.3.3 Syntax Errors and Debugging

Checkpoint 2.3.5.

Checkpoint 2.3.6.

Checkpoint 2.3.7.

Checkpoint 2.3.8.

Checkpoint 2.3.9.

Subsection 2.3.4 Comments

Subsection 2.3.5 Summary

Subsection 2.3.6 Practice

Checkpoint 2.3.10.

Checkpoint 2.3.11.