[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 ckeen):

 Replying to [comment:4 sjamaan]:
 > More to the point: I agree with Moritz that it would be a useful thing
 to have more informative error objects. Christian's suggestion of first
 checking if the file exists is a workaround and opens up a race condition.

 True, that's maybe a bad example and beside my main point.

 Question is: How would programmers deal with it other than now?

 To stick to Moritz's example, how does a more detailed condition type ease
 the situation? If your program assumes that the file is there and now it
 isn't what are you going to do? Fail silently or try to fix the situation
 hoping the user does not notice? And if you are to fix the situation
 silently, how does a better description help there?

 In my eyes this will lead to awkward code where I do a call like this and
 then have lots of branches handling every condition I think I need. Makes
 it very similar to Java...

 If adding another detailed condition type helps, go for it. I am not
 convinced (yet), but happy to hear how you think this helps. I do have an
 open mind...

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