From: brogoff <brogoff@speakeasy.net>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Today's inflamatory opinion: exceptions are bad
Date: Sun, 10 Dec 2006 11:07:05 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0612101049450.31160@shell3.speakeasy.net> (raw)
In-Reply-To: <200612100632.02292.jon@ffconsultancy.com>
On Sun, 10 Dec 2006, Jon Harrop wrote:
> This has been done. There was a tool called ocamlexc that did whole-program
> analysis to find out which exceptions could propagate where. However, it
> wasn't useful enough to be kept up to date.
I think the fact is that it was never part of the main distribution, and
quickly became out of date. That it wasn't or wouldn't have been useful
is a conclusion that you've drawn which is arguable.
If ocamlexc were part of the distr I'd have it run against all the
programs I build. I'd like the extra checking, but, like Richard Jones,
I don't want to have that in the source code. In all of my Java I use
subclasses of RuntimeException to avoid having to list exceptions.
I'm not convinced by the arguments so far, or even that exceptions are
only for exceptional situations. Is End_of_file really exceptional?
What's the proposed alternative to End_of_file, wrapping results in
option?
-- Brian
next prev parent reply other threads:[~2006-12-10 19:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-10 1:42 Brian Hurt
2006-12-10 2:40 ` [Caml-list] " skaller
2006-12-10 2:51 ` Martin Jambon
2006-12-10 3:35 ` Chris King
2006-12-10 6:32 ` Jon Harrop
2006-12-10 19:07 ` brogoff [this message]
2006-12-10 18:04 ` Richard Jones
2006-12-10 23:27 ` Chris King
2006-12-11 15:55 ` Richard Jones
2006-12-15 11:13 ` Frédéric Gava
2006-12-11 17:28 ` Mike Lin
2006-12-11 20:09 ` Richard Jones
2006-12-11 23:38 ` Olivier Andrieu
[not found] ` <C841DA73-83D4-4CDD-BF4A-EA803C6D6A08@vub.ac.be>
2006-12-23 4:23 ` Ocaml checked exceptions Chris King
2006-12-10 6:30 ` [Caml-list] Today's inflamatory opinion: exceptions are bad malc
2006-12-10 6:36 ` malc
2006-12-10 6:56 ` Jon Harrop
2006-12-10 9:51 ` Andreas Rossberg
2006-12-10 11:00 ` Tom
2006-12-10 11:25 ` Andreas Rossberg
2006-12-10 13:27 ` Jean-Christophe Filliatre
2006-12-10 19:15 ` Haoyang Wang
2006-12-10 21:43 ` Jean-Christophe Filliatre
2006-12-11 13:10 ` Diego Olivier FERNANDEZ PONS
2006-12-10 18:31 ` Serge Aleynikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0612101049450.31160@shell3.speakeasy.net \
--to=brogoff@speakeasy.net \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox