[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] #416: Make stock errors more usable programmatically
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] #416: Make stock errors more usable programmatically |
Date: |
Sat, 23 Oct 2010 11:46:53 -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
Keywords: |
----------------------------+-----------------------------------------------
If I call {{{(with-input-from-file "foo" read)}}} with foo being a non-
existant file, I get the following exception:
{{{
condition: (exn i/o file)
exn
message: "cannot open file - No such file or directory"
arguments: ("foo")
location: open-input-file
i/o
file
}}}
The actual cause of this file i/o error was that the file didn't exist,
however, only the error message containts this information. It would be
nice if there was an additional property (maybe a symbol) that would allow
for better programmatic handling of this other than the message itself
(which is likely to change in future versions). This probably applies to
other errors in the core, as well. This is mainly a suggestion. Any
comments or better ideas?
--
Ticket URL: <http://bugs.call-cc.org/ticket/416>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-janitors] #416: Make stock errors more usable programmatically,
Chicken Trac <=