Command: crash_message
  
Syntax: 
  crash_message(s)
  
Description: 
  Specify a string, s, to be printed on the screen in the event
  that Euphoria must stop your program due to a compile-time or
  run-time error. 
  
Comments: 
  Normally Euphoria prints a diagnostic message such as 
  "syntax error" or "divide by zero" on the screen, as well as 
  dumping debugging information into "ex.err". Euphoria's error 
  messages will not be meaningful for your users unless they
  happen to be Euphoria programmers. By calling crash_message()
  you can control the message that will appear on the screen.
  Debugging information will still be stored in ex.err. You won't
  lose any information by doing this.
  
  s may contain '\n', new-line characters so your message can
  span several lines on the screen. Euphoria will switch to the
  top of a clear text-mode screen before printing your message.
  
  You can call crash_message() as many times as you like from
  different parts of your program. The message specified by the
  last call will be the one displayed.
  
  Your crash message will always be displayed if a compile-time
  error (syntax, undeclared variable etc.) occurs. In the case of
  a run-time error (subscript out of bounds, uninitialized 
  variable, divide by zero etc.) your program must be executed
  by the Complete Edition EX.EXE, or have been bound using
  the Complete Edition PDEX.EXE, or be under 300 statements.
  
Example: 
     crash_message("An unexpected error has occurred!\n" &
     "Please contact john_doe@whoops.com\n" & 
     "Do not delete the file \"ex.err\".\n")
 
See Also: 
  abort
  Debugging section of refman.doc
  
