It is frequently not too hard to track down the cause of RB assertion
failure; I've nailed more than one. As I recall, many of them were due
to RS' failure to anticipate some utter stupidity on my part.
Since quality is your duty, you need to add the ability to do debugging
in your code. At a minimum, you should be able to identify the method
call which results in an assertion failure.
As for the dialog, it pinpoints the exact location of the assertion
failure. If you can tell RS how you got there, they can frequently fix
the assertion failure.
Charles Yeomans
On Monday, July 29, 2002, at 03:05 PM, Lo Saeteurn wrote:
I have a great feature request for those of you who are like me that is
sick and tired of those failure assertion that pops up everywhere, but
nearly impossible to fix. With a failure assertion exception, we can
finally track down where it happens instead of quitting or stuck trying
to track it down. It'll help us fix our code and help Real Software fix
the failure assertion since we know what the cause is by tracking it
down.
Don't know why RS had that annoying dialog in the first place that
helps no one!
I'll get it sent right away!
Regards,
Lo Saeteurn
--
Lo Saeteurn
CEO Mien Software
Quality is Our Duty!
http://www.miennetwork.com
|