Difference between revisions of "83Plus:BCALLs:402D"

From WikiTI
Jump to: navigation, search
(more details; I'm not sure what this routine is for)
m (Comments: typo)
 
Line 17: Line 17:
  
 
== Comments ==
 
== Comments ==
This routine is sometimes used by the OS as an error handler.  It's very similar to [[83Plus:83Plus:BCALLs:4048|monErrHand]], and I'm not sure why  this routine would ever be used instead.
+
This routine is sometimes used by the OS as an error handler.  It's very similar to [[83Plus:BCALLs:4048|monErrHand]], and I'm not sure why  this routine would ever be used instead.
  
 
Unlike monErrHand, this routine begins by resetting the hardware stack (but does ''not'' reset the FPS, OPS, or errSP.)  It then loads the "cxError" context, and jumps to [[83Plus:BCALLs:401E|Mon]].
 
Unlike monErrHand, this routine begins by resetting the hardware stack (but does ''not'' reset the FPS, OPS, or errSP.)  It then loads the "cxError" context, and jumps to [[83Plus:BCALLs:401E|Mon]].
  
 
Programs should never call or jump to this routine; I have no idea why it's a B_CALL at all.  If you want to raise a system error, use [[83Plus:BCALLs:44D7|JError]], [[83Plus:BCALLs:4000|JErrorNo]], or one of the specialized error routines.
 
Programs should never call or jump to this routine; I have no idea why it's a B_CALL at all.  If you want to raise a system error, use [[83Plus:BCALLs:44D7|JError]], [[83Plus:BCALLs:4000|JErrorNo]], or one of the specialized error routines.

Latest revision as of 19:47, 29 September 2009

Synopsis

Official Name: sysErrHandler

BCALL Address: 402D

An error handler which displays the standard "ERR:" screen.

Inputs

Outputs

  • None

Destroys

  • Everything (this routine does not return)

Comments

This routine is sometimes used by the OS as an error handler. It's very similar to monErrHand, and I'm not sure why this routine would ever be used instead.

Unlike monErrHand, this routine begins by resetting the hardware stack (but does not reset the FPS, OPS, or errSP.) It then loads the "cxError" context, and jumps to Mon.

Programs should never call or jump to this routine; I have no idea why it's a B_CALL at all. If you want to raise a system error, use JError, JErrorNo, or one of the specialized error routines.