klondike schrieb:
Henning Thielemann escribió:
It seems again to me, that mixing of (programming) errors and
exceptions is going on, and I assumed that the purpose of
control-monad-exception is to separate them in a better way.
You know, could you tell me when using head on an empty list is
klondike schrieb:
Now comes the time when I have to show you that not every exception
could be handled, IE a file not found exception when looking for the
config file can be fatal and force the program to stop. But what if this
is on a library? How do you suggest that the programmer knows
Ah, I had been meaning to read your article, so I appreciate you posting the
link to it a second time. :-)
Out of curiosity, how would you classify an error that results from a
perfectly fine program, but ill-formed user input, such as when compiling a
source file?
Cheers,
Greg
On Dec 7,
Gregory Crosswhite schrieb:
Ah, I had been meaning to read your article, so I appreciate you posting the
link to it a second time. :-)
Out of curiosity, how would you classify an error that results from a
perfectly fine program, but ill-formed user input, such as when compiling a
source
Henning Thielemann escribió:
A library function that reads a config file may declare to be able to
throw the exception File not found, or it may introduce a new
exception Could not read Config file with an extra field for the
reason, why the file could not be read. This way you can construct a
2009/12/07 klondike klondikehaskellc...@xiscosoft.es:
Well I got used to going back to the previous state without
crashing when I got a precondition violation due to user
input. Though I assume that was asking a bit too much of
Haskell.
It's too much to ask of partial functions. If you want
Excerpts from Michael Snoyman's message of Sat Nov 07 22:55:14 +0100 2009:
On Sat, Nov 7, 2009 at 9:54 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Sat, 7 Nov 2009, Jose Iborra wrote:
Sorry for the confusion, I never meant that c-m-e can show stack traces
for
Luke Palmer escribió:
On Fri, Nov 6, 2009 at 6:54 PM, klondike
klondikehaskellc...@xiscosoft.es wrote:
Henning Thielemann escribió:
That's what I meant with my post: Programming errors (like head [])
are not handled by control-monad-exception. As far as I understand,
When using happstack, I find it really annoying to get a
Prelude.head: null list error (or similar) in my web browser window
because somewhere, some library used something unsafe -- and of
course, since this is haskell, no stack trace.
if c-m-e can offer benefits around this, I would be
On Sat, 7 Nov 2009, Jose Iborra wrote:
Sorry for the confusion, I never meant that c-m-e can show stack traces for
asynchronous exceptions. It can not.
My post was not related in any way to asynchronous exceptions. It's just
the everlasting issue of the distinction of programming errors and
On Sat, Nov 7, 2009 at 9:54 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Sat, 7 Nov 2009, Jose Iborra wrote:
Sorry for the confusion, I never meant that c-m-e can show stack traces
for asynchronous exceptions. It can not.
My post was not related in any way to
On Tue, 3 Nov 2009, Jose Iborra wrote:
On 03/11/2009, at 14:24, Henning Thielemann wrote:
Sure, this is a nice functionality. But isn't it about debugging, not
exception handling? Internal Server Error means to me, the server has a
bug, thus we want to know, how to reproduce it, thus the
Jose Iborra schrieb:
Folks,
I'm happy to announce a new release of control-monad-exception with
monadic call traces,
available in Hackage. Grab it now while it is still online!
Monadic stack traces are described in detail in a blog post [1].
In short, what this means for your code is
When using happstack, I find it really annoying to get a Prelude.head:
null list error (or similar) in my web browser window because
somewhere, some library used something unsafe -- and of course, since
this is haskell, no stack trace.
if c-m-e can offer benefits around this, I would be very
On 03/11/2009, at 14:24, Henning Thielemann wrote:
Jose Iborra schrieb:
Folks,
I'm happy to announce a new release of control-monad-exception with
monadic call traces,
available in Hackage. Grab it now while it is still online!
Monadic stack traces are described in detail in a blog post [1].
15 matches
Mail list logo
