On Mar 05, 2006, at 9:54 AM, Joseph J. Strout wrote:
I respect your right to disagree, and your point is valid, but I feel
a need to pick one nit -- failing to return true may always be an
error in YOUR code, but it's generally not in my code. I sometimes
omit the return statement intentionally; since it's done
intentionally, based on the documented behavior of the language, and
has the effect I want, it is not an error.
However, I'm fairly willing to admit that it's a bad habit, even if
it's not an error. In that case, making it a compiler error wouldn't
be terrible.
A per project user settable option to flag missing return values would
solve this wouldn't it ?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
