Quote:
Yup. Failing to return a specific value from a function of type int is bad, and in the case of main() it should be explicitly return EXIT_SUCCESS;

Quote:Original post by ScottMayo
Failing to return a specific value from a function of type int is bad

Quote:
3.6.1 Main function (5)

A return statement in main has the effect of leaving the main function (destroying any objects with automatic storage duration) and calling std::exit with the return value as the argument. If control reaches the end of main without encountering a return statement, the effect is that of executing
return 0;

Quote:
3.6.1 Main function (5)

...If control reaches the end of main without encountering a return statement, the effect is that of executing
return 0;

Quote:Original post by swiftcoder

Quote:Original post by DevFred
I thought about reinterpret_cast, but the result of that would be just as unspecified, wouldn't it ;)

Doesn't casting a pointer to an integer immediately take you all the way into the realm of 'undefined'?

Quote:
A pointer can be explicitly converted to any integral type large enough to hold it. The mapping function is implementation-defined....

A value of integral type or enumeration type can be explicitly converted to a pointer. A pointer converted to an integer of sufficient size (if any such exists on the implementation) and back to the same pointer type will have its original value; mappings between pointers and integers are otherwise implementation-defined.

Quote:Original post by swiftcoder
It is the 'correct' part that keeps tripping you up - return 0 is equally correct, the standard guarantees it [smile]