Re: crash message in 4.0
- Posted by mattlewis (admin) Aug 17, 2008
- 903 views
ne1uno said...
?1/0 produces a full ex.err, crash() is limited since the actual crash is in error.e, which is just confusing. although you do get the message, you don't get your program and function state.
when translated, ?1/0 is confusing, you tried to divide by zero
while crash("error happened in xyz") makes more sense on the console and ex.err but when translated, of course, you get no program internal details.
unless I'm doing it wrong.
Yes, the first thing reported is crash, since that's where it happened. But the rest of the stack trace is there. If this is still unacceptable, you can call machine_proc directly, without the std/error.e wrapper.
Matt
