On Mar 2, 2006, at 4:21 PM, Thomas Cunningham wrote:
Really? What would be the downside? Seems to me, a routine that is declared as a function that does not return a value is an error plain and simple.
There are a number of cases where a return value is not expect, such as with the Events that expect a Boolean if you handle the event. This would basically render a Event that returns a value to be useless since all of those events must have some code.
What would be a useful compromise between the solution you suggest and the current behavior is to allow the compiler to give a *warning* for any *function* (not sub) that does not have at least one return statement, and only if the function/event contains code. The warning would just be a warning and the compiler would continue to launch the debug app.
_______________________________________________ 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>
