Michael Snoyman schrieb:
On Mon, Dec 7, 2009 at 5:30 AM, Ben Franksen ben.frank...@online.de
mailto:ben.frank...@online.de wrote:
Michael Snoyman wrote:
On the other hand, what's so bad about treating errors as exceptions? If
instead of the program crashing on an
On Mon, Dec 7, 2009 at 2:13 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
Michael Snoyman schrieb:
On Mon, Dec 7, 2009 at 5:30 AM, Ben Franksen ben.frank...@online.de
mailto:ben.frank...@online.de wrote:
Michael Snoyman wrote:
On the other hand, what's so
On Mon, 7 Dec 2009, Michael Snoyman wrote:
The only opinion I've stated so far is that it's ridiculous to constantly demand
that people follow your definition of error vs exception, since the line is
incredibly
blurry and it buys you very little.
If you have an example that is not contained
On Mon, Dec 7, 2009 at 9:07 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Mon, 7 Dec 2009, Michael Snoyman wrote:
The only opinion I've stated so far is that it's ridiculous to constantly
demand
that people follow your definition of error vs exception, since the line
is
I turn it around: give me an example where it's better for the runtime to exit
than for
some type of exception to be thrown, and *I'll* think about it ;).
If you would have read my article, you had one ...
___
Haskell-Cafe mailing list
On Mon, 7 Dec 2009, Michael Snoyman wrote:
I actually *did* read your article, and don't know what you are referring to.
If this is true, sorry, I didn't had the impression.
I also think that in an earlier mail I answered, that errors can leave you
with corrupt data, say invalid file
On Mon, Dec 7, 2009 at 9:53 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Mon, 7 Dec 2009, Michael Snoyman wrote:
I actually *did* read your article, and don't know what you are referring
to.
If this is true, sorry, I didn't had the impression.
I also think that in an
When I was working at Quintus, I came up with a classification
which I can simplify something like this:
operating system fault
Something bad happened (like a remote node going down) that was
entirely out of your control. There is nothing you can do to
your program to
Michael Snoyman wrote:
On Mon, Dec 7, 2009 at 9:53 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Mon, 7 Dec 2009, Michael Snoyman wrote:
I also think that in an earlier mail I answered, that errors can leave
you with corrupt data, say invalid file handles, memory pointers,
On Tue, 8 Dec 2009, Richard O'Keefe wrote:
When I was working at Quintus, I came up with a classification
which I can simplify something like this:
It's certainly possible to classify errors and exceptions in other (also
more fine grained) ways ...
operating system fault
On Dec 8, 2009, at 12:28 PM, Henning Thielemann wrote:
representation faults
your program tried to do something meaningful but the system
was unable to represent the result (integer overflow, upper
case of ΓΏ in a Latin 1 system, floating point overflow on a
On Tue, 8 Dec 2009, Ben Franksen wrote:
Michael, Henning
There are two meanings to the word 'exception' in this context; both of you
tend to conflate these different meanings. One meaning is about a
*mechanism* for non-local control flow; the other is about certain classes
of un-desired
On Tue, 8 Dec 2009, Richard O'Keefe wrote:
X/0, sqrt(-1), head [] are errors
It depends on WHERE THE DATA CAME FROM.
If your program actually computes X/0 or sqrt(-1) or head [] your program
is buggy, independent from where the zero, the minus one or the empty list
comes.
Sure, the
On Tue, 8 Dec 2009, Richard O'Keefe wrote:
On Dec 8, 2009, at 12:28 PM, Henning Thielemann wrote:
It is the responsibility of the programmer to choose number types that are
appropriate for the application. If I address pixels on a todays screen I
will have to choose at least Word16. On
On Dec 8, 2009, at 1:27 PM, Henning Thielemann wrote:
On Tue, 8 Dec 2009, Richard O'Keefe wrote:
On Dec 8, 2009, at 12:28 PM, Henning Thielemann wrote:
It is the responsibility of the programmer to choose number types
that are appropriate for the application. If I address pixels on a
I'm wondering, what are we talking about here?
- the meaning of error and exception?
- personal responsibility when writing programs?
- language features - library functions, runtime implementation etc.?
The first two, I think could serve as the basis for an entertaining
discussion. Where
On Tue, Dec 8, 2009 at 1:25 AM, Ben Franksen ben.frank...@online.de wrote:
Michael Snoyman wrote:
On Mon, Dec 7, 2009 at 9:53 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Mon, 7 Dec 2009, Michael Snoyman wrote:
I also think that in an earlier mail I answered, that
On Tue, Dec 8, 2009 at 7:40 AM, Michael Snoyman mich...@snoyman.com wrote:
On Tue, Dec 8, 2009 at 1:25 AM, Ben Franksen ben.frank...@online.dewrote:
Michael Snoyman wrote:
On Mon, Dec 7, 2009 at 9:53 PM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Mon, 7 Dec 2009,
Michael Snoyman wrote:
On Sun, Dec 6, 2009 at 12:55 AM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Sun, 6 Dec 2009, Michael Snoyman wrote:
I think there are plenty of examples like web servers. A text editor
with
plugins? I
don't want to lose three hours worth of work
On Mon, Dec 7, 2009 at 5:30 AM, Ben Franksen ben.frank...@online.de wrote:
Michael Snoyman wrote:
On Sun, Dec 6, 2009 at 12:55 AM, Henning Thielemann
lemm...@henning-thielemann.de wrote:
On Sun, 6 Dec 2009, Michael Snoyman wrote:
I think there are plenty of examples like web servers. A
20 matches
Mail list logo
