Nathan Ridge wrote:
Why does gcc not give an error about this?
If I compile with "-Wall", it will give a WARNING saying
"control reaches end of non-void function".
However, shouldn't it be an ERROR to return nothing
from a function that's supposed to return something?
Does this not result in undefined behaviour? Why goes gcc allow it?
Because the standard does not make this an error, you can't tell
if anyone needs a result, perhaps function is always called in
a void environment.
A warning is all you can get, always pay attention to warnings!
Thanks,
Nate.
_________________________________________________________________
Share photos with friends on Windows Live Messenger
http://go.microsoft.com/?linkid=9650734
