OpenEuphoria

Re: Request for feature

• Posted by "Gregory Haberek" <ghaberek at gmail.com> Dec 27, 2007
• 489 views

> Sure, abort() is here already, so let's extend it:
> * abort(msg_string) would display msg_string and do an abort(-1);
> * abort({string,ret_val}) would display msg_string and do an abort(ret_val).
>
> How about that?

crash_message() already sets up the message to be displayed.
Currently, I could do something like this:

crash_message("An internal error has occurred.")
? 1/0

I could also then hack up the ex.err file in my crash routine, cutting
out the "divide by zero" error, thus accomplishing what I'm asking,
but... it seems easier to simply add a new feature to the interpreter.

Also, I think it'd be best to keep abort() for safe exits and crash()
for bad exits. I can already "abort" the interpreter, I'd like to be
able to "crash" it, too.

-Greg