caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Mike Lin" <mikelin@mit.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Today's inflamatory opinion: exceptions are bad
Date: Mon, 11 Dec 2006 12:28:05 -0500	[thread overview]
Message-ID: <2a1a1a0c0612110928q54567a7fld4e0d9afc9845f62@mail.gmail.com> (raw)
In-Reply-To: <20061210180426.GA5347@furbychan.cocan.org>

[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]

Reasonable people can certainly dislike checked exceptions, but if you're
against them, then you should at least demand that your goddamned runtime
system tell you where exceptions are coming from. Is Markus Mottl's patch
making OCaml 3.10? Bueller? Bueller?

On 12/10/06, Richard Jones <rich@annexia.org> wrote:
>
> On Sat, Dec 09, 2006 at 10:35:56PM -0500, Chris King wrote:
> > One thing Java (sort of) gets right is keeping track of which
> > exceptions a function can throw, making it easy to ensure that some
> > deeply nested piece of code won't cause the entire application to die
> > from some obscure exception.  I'd love to see a similar feature in
> > O'Caml, whereby the exceptions which a function can raise are part of
> > its type and are inferred and checked by the compiler.
>
> Oh please no!  Checked exceptions are the dumbest and most frustrating
> feature of Java (and that's saying something - the Java language has
> far more frustrations than most programming languages).
>
> Rich.
>
> --
> Richard Jones, CTO Merjis Ltd.
> Merjis - web marketing and technology - http://merjis.com
> Internet Marketing and AdWords courses - http://merjis.com/courses - NEW!
> Merjis blog - http://blog.merjis.com - NEW!
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 2209 bytes --]

  parent reply	other threads:[~2006-12-11 17:28 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
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 [this message]
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=2a1a1a0c0612110928q54567a7fld4e0d9afc9845f62@mail.gmail.com \
    --to=mikelin@mit.edu \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).