[Chicken-janitors] Re: #416: Make stock errors more usable programmatically

[Chicken Trac]

#416: Make stock errors more usable programmatically
-----------------------------+----------------------------------------------
  Reporter:  syn             |       Owner:       
      Type:  enhancement     |      Status:  new  
  Priority:  minor           |   Milestone:  4.7.0
 Component:  core libraries  |     Version:  4.6.x
Resolution:                  |    Keywords:       
-----------------------------+----------------------------------------------

Comment(by felix):

 I agree with Peter that this may be more of a hassle than it initially
 seems. There are countless possible error situations and it might be
 better to explicitly test for those. Some basic context can be found from
 the condition-type (used in `condition-case` to dispatch to the different
 clauses). We could perhaps differentiate those somewhat (something like
 `(exn i/o file nonexistant)` for example). Would that be an acceptable
 compromise? Which situations should be distinguished then?

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/416#comment:2>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.