Welcome to the Lounge

honey the codewitch wrote:

Interestingly you can call main() from inside your C app, but not in C++.

• There are multiple valid forms of main(...), and implementation-defined arguments are allowed. Allowing calls to it might require too much special case handling between the compiler and linker to ensure a match between the call and the actual implementation.
• Another factor might be runtime initialization that takes place in main()'s prolog.
• Objects declared static could potentially call main() before it had been called for the actual application startup.

int main()
{
  main();
}

honey the codewitch wrote:

Interestingly you can call main() from inside your C app, but not in C++.

int fn(){
int a;
return(0);
}

void fn
{
int a;
}

3.6.6.4 The return statement
...
Reaching the } that terminates a function is equivalent to executing a return statement without an expression.

mdblack98 wrote:

Reaching the } that terminates a function is equivalent to executing a return statement without an expression.

"Flowing off the end of a function is equivalent to a return with no returned value."

• Owen -

Juan Pablo Reyes Altamirano wrote:

So when C++ introduced void as a return type, even for main

{
   int x;
   x = 42;
   return x; // ok
   return x + 1; // does not compile because x + 1 is an expression
   return(x + 1); // ok, the expression is evaluated by the compiler

sx2008 wrote:

You should NOT write these unnesseccary parentheses anymore!

sx2008 wrote:

The return statement is not a function call; just omit the parentheses.

ReTuRn("December");  // this is a function call
return("December");  // this is a return statement

Quote:

You can write a C program on one line by removing those unnecessary end of line characters but that is not a good idea either.

return ((((0))));  // valid code, but stupid
return ((0));      // still stupid
return 0;          // that's the way to go