Changes between Version 10 and Version 11 of ExceptionHandlingCowan


Ignore:
Timestamp:
08/17/10 07:00:13 (7 years ago)
Author:
cowan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ExceptionHandlingCowan

    v10 v11  
    11= Design = 
    22 
    3 When a problem situation, or ''exception'', is detected 
    4 either by the implementation or by a 
     3When a situation calling for exceptional handling is 
     4detected either by the implementation or by a 
    55user program, a representation of that situation called a ''condition'' 
    66(which can be any Scheme object) is constructed, and the exception is 
     
    6868The `who` argument must be a string or a symbol that describes the procedure or operation that detected the exception. The ''message'' argument must be a string that describes the exceptional situation. The ''irritants'' should be the arguments to the operation that detected the operation, but may be any objects relevant to the exception. 
    6969 
    70 The predicates `who-condition?`, `message-condition?` 
    71 and `irritants-condition?` return `#t` on this condition. 
    72  
    7370  * `(error `''message''`. ` ''irritants''`)` 
    7471 
     
    7774 
    7875The ''message'' argument must be a string that describes the exceptional situation. The ''irritants'' should be the arguments to the operation that detected the operation, but may be any objects relevant to the exception. 
    79  
    80 The predicates `message-condition?` 
    81 and `irritants-condition?` return `#t` on this condition. 
    8276  
    8377 
     
    8680Thanks to Taylor Campbell, Alaric Snell-Pym as the author of 
    8781ErrorsSnellPym, Kent Pitman as the author of the ISLisp specification, 
    88 and the editors of R6RS, 
     82and the editors of R6RS and the ANSI CL standard, 
    8983from all of whom I have derived inspiration and stolen descriptions.  They bear no responsibility 
    9084for infelicities in this proposal.