Well the type of failure assertion errors I get doesn't even crash the
app (most of the time). The app continue running just fine. Sometimes it
just continuously shows the dialog, but when I break into IDE it can
still run (but it becomes less stable), meaning we can still a least see
where the error occurred with the exception.
Maybe instead, it should still show the dialog, but if you click
continue, the exception error would occur. i don't see any downside with
this.
On Monday, July 29, 2002, at 12:21 PM, Will Leshner wrote:
The problem is that by the time you get a failed assertion things are
so messed up that running reliably beyond that point is impossible. The
annoying dialog helps RS if we send in the line number and file name to
them.
On Monday, July 29, 2002, at 12: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.
---
Subscribe to the digest: <mailto:realbasic-dr-
digest at lists dot realsoftware dot com>
Unsubscribe:
<mailto:realbasic-dr-off at lists dot realsoftware dot com>
Regards,
Lo Saeteurn
--
Lo Saeteurn
CEO Mien Software
Quality is Our Duty!
http://www.miennetwork.com
|