Thread: What is that at the end of a method

Ok so i have been independent here for little while and that seems to be my only option and the thing is reading something doesn't usually do it for me i dont take in information from reading, especially with a lot of terminology involved. Which is an awful problem
for trying to learn programming.
Anyways ive been jumping around and starting to grasp some things pretty well (i may not be actually i just think i am).

Question is, what is the stuff that is red at the end of the method(if thats even called a method i hope im not that confused with the vocab).

static void main(String[] args)

If you must use terminology to explain something try to keep it light but dont keep it all out i will need to understand all the terminology at some point as well. but DO tell me what this red is called in terminology so i will have a more direct way of finding info on it.

I want to know what this is as in any method not particularly this one, i remember reading something about this one taking arguments from the command line interface? anyways what is that red stuff and how important is it to know and understand.

sorry about the jumbled question im in a hurry sort of, and thanks for the help.

Okay that is the parameters of a method.


accessControl returnType name(Parameters)

That is the basic of a method. To break it down

• Access Control: Can other classes access this method? More Info
• Return Type: What type will this method return? More Info
• Parameters: What information is passed to the method called More Info

Other Recommended Reading
Defining Methods (The Java™ Tutorials > Learning the Java Language > Classes and Objects)
Java Programmer's SourceBook : Thinking in Java

Ok so its Parameters that get me.

Ok so i understand i think?
So what your doing is passing information to the method, and when it is passed from whatever variable it may be or object the values are sort of copied not actually directly changed by the method that use them? is that all correct?
I guess what im looking for is an example that can be explained why the parameters are put there.

Ok so why would you not just create the variable in the method, why use parameters?

oh ok atleast i might understand one part of this whole picture, i apologize for being such a slow learner.

so if i had a method and all i wanted the method to do was take some Item objects and find if there slots are available by changing it true or false, it may look something like this.


public boolean Availability(Item item1, Item item2, Item item3){
//some code that determines if an item is there in that item slot
if (there be an item there){
return false;
}
else{
return true;
}
}

Originally Posted by poetzmij

oh ok atleast i might understand one part of this whole picture, i apologize for being such a slow learner.

so if i had a method and all i wanted the method to do was take some Item objects and find if there slots are available by changing it true or false, it may look something like this.


public boolean Availability(Item item1, Item item2, Item item3){
//some code that determines if an item is there in that item slot
if (there be an item there){
return false;
}
else{
return true;
}
}

Dpending upon, if you want your method to return false in case, it finds the Item, the pseudocode is FINE.