Maximum PC

I've tried googling it, I can't seem to find any relevant results.

How do I create procedures in Java? Basically I want to name a block of code and be able to call upon and execute that code when needed.

I can only think of creating a new object and placing the aforementioned code in that object. Then refer to the object you just created when you want to run that code. That's how I learned it anyway. Sorry if that's not really anything like want you want to do.

You're looking for functions. Don't worry that they're all marked public static for now, as that will become more relevant when you learn more.

OK, thanks that worked, but I have another question, is there a way of declaring a variable, and having that variable be able to be accessed anyplace in the program? Even if its in a different function?

Declare the variable as static inside a class:

If I do that, it says: This static variable declaration is invalid, because it is not final, but is enclosed in an inner class.

Declare the variable at the same level as the functions, inside of that same class instead of nesting the classes.

Actually, otherFunction is a procedure, not a function. Functions return values, procudes work based on side-effects... come on, you're not old enough to be forgetting this stuff yet Smartcat!

This is the biggest problem using Java as a teaching language. =\

It looks like you're trying to use an object oriented language to write a non-object oriented program. There are a few instances where static functions and variables make sense, but their use should be more the exception than the rule. You may want to re-think how you're approaching the problem...or pick a language that's more suited to how you logically break down problems into algorithms.

I started in java and still have problems with oop. then again i can barely program. either way.

Dwood15 -- Java is actually a pretty damn good language in which to learn OOP. I would highly recommend that you spend some time with Bruce Eckel's Thinking in Java book -- he does a very good job of explaining the concepts w/o screwing things up with unnecessary crud (like using an applet to explain some OOP concept).

I listed it in the starting out thread or google it.

I disagree. There are plenty of instances where static methods are the correct choice. The use of static methods and static variables depends entirely on what you are doing. Would rewrite java.lang.Math? Making everything static is surely a sign of a bad design, but it sounds like you're tilting pretty far in the opposite direction which is also a mistake.