--- Comment #15 from Witold Baryluk <> 2010-02-05 
05:28:30 PST ---
(In reply to comment #14)
> Exception handling is for error conditions, not flow control.  If someone is
> actually constructing exceptions for some other purpose then they're using the
> wrong tool :-)

Well, yes you are right. I just checked my old code which i was thinking is
using heavly EH for flow control. But I wasn't so stupid :) EH is only used for
escaping in rare ocasions (not for error conditions but for flow control, yes,
but i'm comparing more throw here to break; like in for/while, than to
continiue :) )

Sorry for the problem. 

Anyway in documentation of this functionality I think there should be the
statment that stacktrace is only intended to help in debuging and crash
reporting, and no code should directly depend on the fact  that returned
backtrace is nonempty or correct. (becuase in one can set traceHandler to null,
or disabled it in -release mode for example).

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to