On Dec 8, 2006, at 11:28 AM, Joe Huber wrote:
At 8:58 AM -0700 12/8/06, Norman Palardy wrote:
There are a couple bug reports / feature request that you might
sign on to that are relevant
http://www.realsoftware.com/feedback/viewreport.php?reportid=vivheyfz
http://www.realsoftware.com/feedback/viewreport.php?reportid=whhwkwpg
FWIW This related bug is marked fixed in 2006r3
http://support.realsoftware.com/feedback/viewreport.php?
reportid=bbabwtah
I'm not sure if trying to access the array by index is considered
"Calling a method on the array", which is what's stated to have
been fixed.
Okay, a lightbulb moment just happened... Try the following:
see if you can call a 'method' on the nil array and see if it
produces an NilObjectException. If you can trap that instead, you
could then make a bit of code to test for a nil array indirectly by
adding and then removing a junk value from the array within a Try-
Catch block (or the old style 'Exception e As RuntimeException'
handler at the bottom of the method). If the array is nil, the test
should blow up when you call <array>.Append, but if not, the append
and subsequent ,remove will leave the array in the same state it was
in when you began, assuming you .append and .remove data of the
appropriate data type for the array.
It sounds like you can still get a Nil array, but it shouldn't be
crashing when you try to access it. You should get a NOE instead.
Regards,
Joe Huber
_______________________________________________
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>
_______________________________________________
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>
