(Posting reorganized to eliminate top-posting)
/* Put this in DustWolf.java */
public class DustWolf {
public static void main(String args[]) {
int n1 = 18;
int n2 = 36;
System.out.println("The sum of " + n1 + " and " + n2 + " is: " +
Helper.add(n1, n2));
}
}'
/* Put this in Helper.java */
public class Helper {
public static int add(int a, int b) {
return a + b;
}
}
/* Compile with:
javac -classpath . Helper.java DustWolf.java
Execute with:
java -classpath . DustWolf
*/
Bear in mind that the simplified example appears to endorse putting classes in
the default package, which is a well-known Bad Idea. It's may seem like a
complication if you're learning the basics of the "public" keyword, how to put
source into ".java" files and how to use javac, but it is just as important to
learn about packages as these other concepts.
To the OP: a "package" is related to what subdirectory the class file is in.
The simplified example put all the source code into the "default package",
which corresponded to the current directory "." mentioned in the "-classpath"
variables. When you feel more comfortable with how to declare a method
"public", how to organize source into ".java" files and the other basics of
the Java(tm) language, you will need to understand about subdirectories and
packages. The result will be something like:
/* Put this in somewhere/DustWolf.java */
package somewhere;
public class DustWolf {
...
}
/* Put this in somewhere/Helper.java */
package somewhere;
public class Helper {
...
}
/* Compile with:
javac somewhere/Helper.java somewhere/DustWolf.java
Execute with:
java -classpath . somewhere.DustWolf
*/