On Mar 05, 2006, at 11:00 AM, Joseph J. Strout wrote:
At 10:44 AM -0700 3/5/06, Norman Palardy wrote:
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 ?
No! That would be the worst of all possible options. VB has things
like this -- per-project settings that change how the language is
compiled -- and it's a nightmare. It makes it almost impossible to
share code, since code that works fine in one project fails to compile
(or worse, compiles differently!) in another. It is the road to
madness, suffering, and grief.
But this is just whether or not to throw up a warning, not a change to
the compiler nor the language.
Along the lines of Metrowerks panel for what compiler warning to
generate.
I'd agree that I would NEVER want to see the option Base craziness
introduced as that one DOES change how everything is referenced in
arrays and is a real problem for exactly the reason you state.
I'd just like an option to have the compiler warn me if I have missed
return values when I should have been explicitly returning one.
_______________________________________________
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>
