If one has code in a computed property that ( erroneously ) causes a
NilObjectException to be triggered in certain cases, this can cause many
hassles trying to track it down.
The NiloBjectexception occurs when that code is being fired when the
debugger
is attempting to display the compute property value on a breakpoint or
single-step.
This can trigger a nilobject exception but with no clue as to where to look.
The debugger does not automatically break on the exception occurring inside
the computed property.
I realise this can be resolved by coding correctly, but i use computed
properties extensively ( largely to ease the debugging process ) and
occasionally forget to code for nil objects ( I am allegedly human )
Sign on to the following feature request if this is an issue for you:
http://www.realsoftware.com/feedback/viewreport.php?reportid=trrzrwwq
_______________________________________________
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>
|