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

 Replying to [comment:6 ckeen]:
 > 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?

 If it assumes that, it doesn't matter how the condition is structured :)

 > 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?

 You can only fix the situation by catching the relevant errors you know
 how to fix.

 > 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...

 Yeah, that would suck. But then, if you really need differing code for
 handling different situations, I don't see how else to solve it. It seems
 like a fundamental problem of wanting to deal with different situations
 differently.

 > 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...

 Yeah, I'm not sure this would really help. Maybe Moritz can explain how he
 wanted to use this in his code.

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