Why must main() always be static?

Why must main() always be static?

• A. It is the entry point — no object needs to be created to call it
• B. It is always invoked automatically at program start
• C. It can be overridden in a subclass
• D. It must be declared public

Answer: (A)

The main idea is that the starting point of a program must be callable without creating any object. The runtime needs a method it can invoke to begin execution before any instances exist, so the entry point is defined as a static method of a class. Being static ties the method to the class itself rather than to any particular object, allowing the runtime to call ClassName.main(args) directly to start the program. This is why the method is designated as static (and typically public with the signature void main(String[] args) in Java). Other statements don’t capture why this method must be static: calling main automatically at startup is related to the runtime behavior, but the essential requirement is that it be callable without an object. The idea that it can be overridden in a subclass is incorrect for static methods, which aren’t truly overridden. While visibility (public) matters for accessibility, the fundamental reason is its existence as a class-level entry point that doesn’t require object construction.

The main idea is that the starting point of a program must be callable without creating any object. The runtime needs a method it can invoke to begin execution before any instances exist, so the entry point is defined as a static method of a class. Being static ties the method to the class itself rather than to any particular object, allowing the runtime to call ClassName.main(args) directly to start the program. This is why the method is designated as static (and typically public with the signature void main(String[] args) in Java).

Other statements don’t capture why this method must be static: calling main automatically at startup is related to the runtime behavior, but the essential requirement is that it be callable without an object. The idea that it can be overridden in a subclass is incorrect for static methods, which aren’t truly overridden. While visibility (public) matters for accessibility, the fundamental reason is its existence as a class-level entry point that doesn’t require object construction.