[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] Re: #416: Make stock errors more usable programmatica
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] Re: #416: Make stock errors more usable programmatically |
Date: |
Wed, 03 Nov 2010 22:31:03 -0000 |
#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):
I am not sure what you want to do in case of this error. What I would do
in a file selection dialog: catch the condition and present the message to
the user and then try again.
What should a program do if the file does not exist? If I would expect a
file to exist I would do a fstat call first anyhow, so I could create the
file if necessary.
Unless there is a clear advantage in being able to tell the difference
between file not found, file unreachable (network mounts), file unwritable
(permissions or disk full?) and what not, I would like to dodge the issue
at large.
--
Ticket URL: <http://bugs.call-cc.org/ticket/416#comment:1>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
- [Chicken-janitors] Re: #416: Make stock errors more usable programmatically,
Chicken Trac <=