c++standardsprogram-entry-pointlanguage-designentry-point

Why wasn't void main() standardized as a valid signature for the main function?


Why has setting the entry point's return type to void in C++ always been discouraged, and was later removed by the standard and is prohibited by modern compilers? Why is it considered bad practice?

Now, as I understand C# and Java both allow the entry point's return type to be void i.e

static void main(String[] args) /* Java */
static void Main(string[] args) /* C# */

And C# and Java programmers do not consider it bad practice, they use it often in fact.

Other languages which are (only intended to be, I doubt C++ will be succeeded in this decade, at least) possible successors of C++ like the D Programming Language or Vala also allow a void main(). So as you can see, I doubt the C++ community removed it from the standard because it was too obscure or unpopular.

So my question is, Why did the C++ Community Remove void main()? What was wrong with it?


Solution

  • The C++ standards committee likely chose to require int main() because of the large body of existing code that expected to use a return statement to return a specific exit code to the runtime system. It would be unreasonable to expect all existing code to change to use exit() instead, so int main() was made a requirement in the standard.

    A language such as Java, when it was designed, did not have any body of existing code that it needed to remain compatible with. Therefore, the designers could choose void main() and require the use of System.exit() for non-zero exit codes.

    So, the thing that would be "wrong" with choosing void main() for the C++ standard would be that it would break existing code that expected to use return and an exit code value from main().