DIRECTORY PrincOps USING [ControlLink, FrameHandle]; RuntimeError: DEFINITIONS = BEGIN OPEN PrincOps; BoundsFault: ERROR; ControlFault: SIGNAL [source: ControlLink] RETURNS [ControlLink]; DivideCheck: SAFE SIGNAL; LinkageFault: ERROR; PointerFault: ERROR; PortFault: ERROR; ResumeError: SIGNAL; SendMsgSignal: SIGNAL RETURNS [message: WORD, signal: SIGNAL ANY RETURNS ANY]; StartFault: SIGNAL [dest: PROGRAM]; StackError: ERROR; UnboundProcedure: SIGNAL [dest: ControlLink] RETURNS [ControlLink]; UNCAUGHT: SAFE ERROR [signal: SIGNAL ANY RETURNS ANY, parameters: WORD]; ZeroDivisor: SAFE SIGNAL; UCSProc: TYPE = PROC [msg: WORD, signal: SIGNAL ANY RETURNS ANY, frame: FrameHandle]; RegisterUncaughtSignalHandler: PROC [proc: UCSProc] RETURNS [old: UCSProc]; InformationalSignal: SAFE PROC [signal: SIGNAL]; END. RuntimeError.mesa Copyright c 1985 by Xerox Corporation. All rights reserved. Levin on May 25, 1983 5:21 pm Russ Atkinson (RRA) February 19, 1985 1:01:44 pm PST Doug Wyatt, February 26, 1985 3:11:29 pm PST Signals and errors generated by the Mesa runtime raised by the BNDCK instruction raised when a bad control link is discovered raised by overflow on a divide raised by the NILCK or NILCKL instructions raised when an ERROR is resumed used to request the current signal and message inside of an ANY catch phrase ... is typically disastrous, caused by bad or clobbered code ... raised when transfer is attempted to an unbound procedure ... raised when the UncaughtSignalHandler is about to be called. Using UNCAUGHT is much better than handling ANY! UNCAUGHT should be provided by the compiler, eventually. the classic divide by zero signal Related procedures Registration mechanism for the global uncaught signal handling function. This is a temporary kludge that provides a minimal informational signal mechanism. Κo– "Cedar" style˜codešœ™Kšœ Οmœ1™