On Dec 08, 2006, at 8:52 AM, JC wrote:
Yes. Previously my return statement was in a loop that "processed"
the
array. I didn't want to "process" an empty array. So if the array
was
empty I returned nil. However returning the empty array works fine
(i.e. I
took the return statement out of the conditional statement that
protected
the "processing" code. If that makes sense. At the time (well up until
yesterday in fact) I was under the misguided impression that an
empty array
and a nil array were the same thing (superficially as least - the
reality is
I never reflected on the problem long enough to really consider it
in those
terms because in hindsight it appears obvious now).
Regardless I agree the lack of tools to deal with a nil array make it
something to avoid.
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
_______________________________________________
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>
