Question

Why does the main method in Java always need arguments? Why should we write String[] args every time, instead of just writing it when we use any arguments?

A method like this generates Main method not found compiler error. Since we never use any arguments to the main method, this should be allowed.

public static void main()
{
}

This is not an interview question. It just came to my mind while programming.

Answer 1

Basically, there are four answers:

1. Because that’s the way it was designed. Yea, I know that’s a circular reason. But the point is that this is the way it is and it ain’t going to change. So unless you are planning on designing your own language, the question is moot.

2. Cleanness of design (aka the DRY principle). Don’t specify two entry point signatures when one can do the job. And clearly, it can.

3. Semantic simplicity. Suppose (hypothetically) that Java did support both void main(String[]) and void main() entry points. What would happen if a class defined both methods? Is that an error? If not, which one takes precedence when there is ambiguity? Is this confusing yet?

   By only recognizing void main(String[]), the JLS avoids that problem¹.

4. This is analogous to the standard C and C++ entrypoint signatures. (Admittedly, some C / C++ runtimes support other non-standard entrypoints as well, but that’s not exactly a good thing².)

None of this means that it would have been unambiguously wrong to do it another way. And for example C# gives you alternative signatures, and deals with the ambiguity problem by requiring the developer to designate an entry point some other way.

FWIW, this wikipedia page describes the "main" method in a number of languages.

---

<sup>1 – Though then you have the "problem" that people who are new to Java might guess (incorrectly) that multiple entry points ought to work, try it, and get a surprise. But I don’t think any design could cope with "programming by guesswork".

2 – For a start, it is a portability issue.</sup>