On Feb 17, 2006, at 2:07 PM, CV wrote:
There are several Feedback requests pertaining to this issue:
vivheyfz,bbabwtah,hfqqxymn,urvbevct.
It arises when a function returning an array fails to do so due to a
programming error, and it is acknowledged that nil is the intended
return in this situation.
Yet the compiler doesn't flag a nil object exception or even the
catch-all "You must use the return value...", so the result is a
crash(unexpected quit) at runtime.
The debugger is aware of the nil return, so shouldn't this be caught
therein?
This should probably be caught by the compiler since trying to do
dim a() as string
a = nil
won't compile
_______________________________________________
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>
