caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Hurt <brian.hurt@qlogic.com>
To: Ocaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Checked exceptions and type inference
Date: Tue, 11 Mar 2003 15:50:13 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0303111538120.2164-100000@eagle.ancor.com> (raw)


Reading LtU I came across this article:
http://www.octopull.demon.co.uk/java/ExceptionalJava.html

Java treats checked exceptions as part of the type signature of the 
function.  As such, it seems to me that as such, type inference would work 
to propogate most of this information in a more convient way.

Checked exceptions actually have their uses, for "errors" which are not 
very exceptional.  Out of memory is highly unexpected.  End of file isn't 
quite as surprising.  Not_found is another that shouldn't be that 
surprising- although that leads to a different religous war.

Is there any research on using checked exceptions in an ML derived 
language?  Any plans/opinions on implementing checked exceptions in Ocaml?

Brian


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2003-03-11 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 21:50 Brian Hurt [this message]
2003-03-12  5:40 ` Jacques Garrigue
2003-03-12  8:45 ` Xavier Leroy
2003-03-12 10:12   ` Stefano Zacchiroli
2003-03-12 16:34     ` Xavier Leroy
2003-03-12 17:20 ` Richard W.M. Jones
2003-03-12 20:49   ` Brian Hurt
2003-03-12 18:45 ` William Chesters
2003-03-12  3:00 Arturo Borquez
2003-03-12  3:24 ` Nicolas Cannasse
2003-03-12  3:43 ` mgushee

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.33.0303111538120.2164-100000@eagle.ancor.com \
    --to=brian.hurt@qlogic.com \
    --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).