Welcome to the Lounge

Maximilien wrote:

Was it necessary at some point in time ?

void g(int* p);

void h(int* p) { return g(p); }

jschell wrote:

Possible though that earlier compilers required it.

jschell wrote:

void h(int* p) { return g(p); }

void h(int* p)
{
    g(p);
    return; // if you really feel the need
}

Quote:

But I always make sure each and every C function (or C# Method) has exactly one return statement.

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