caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Teller <David.Teller@univ-orleans.fr>
To: "Bünzli Daniel" <daniel.buenzli@erratique.ch>
Cc: caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] [OSR] Exceptionless error management, take 2
Date: Fri, 08 Feb 2008 16:39:45 +0100	[thread overview]
Message-ID: <1202485185.7079.18.camel@Blefuscu> (raw)
In-Reply-To: <AE07C5D5-7AF5-418B-80B0-06E1441E651D@erratique.ch>

On Fri, 2008-02-08 at 13:40 +0100, Bünzli Daniel wrote:
> Le 8 févr. 08 à 12:56, Vincent Hanquez a écrit :
> > If I use normal variant, the compiler will prevent me using the same  
> > code to match a X.Error and a Y.Error.
> 
> Note that with this take 2 proposal -- that I personnaly find too  
> invasive and heavy weight  -- you won't get that, you will have to  
> match on Error.Error (!) instead of `Error (take 1).
> 
> Daniel

Well, I do expect people to do a "open Error" at some point in their
code.

You are correct that `Error is shorter than Error.Error. On the other
hand, if you intend to use `Error and `Success as a standard for
exceptionless error management, you will need to standardise the use of
these specific polymorphic variants for this specific meaning and to
either teach people how to write closed polymorphic variants or expect
them to miss errors every so often. All this in a context where one of
the main objectives is to make error-management easier and safer.

Both systems have drawbacks -- not quite surprising. I believe that
writing "open Error" if there's no ambiguity and "Error.Error" if there
is any is a small price to pay. So for the moment, I stand behind take
2.

Cheers,
 David

P.S.: Everyone, please don't let this thread degenerate into a slugfest
"polymorphic variants are way kool" vs. "polymorphic variants are
obscene".

-- 
David Teller
 Security of Distributed Systems
  http://www.univ-orleans.fr/lifo/Members/David.Teller
 Angry researcher: French Universities need reforms, but the LRU act
brings liquidations. 


  reply	other threads:[~2008-02-08 15:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 15:01 David Teller
2008-02-07 15:09 ` [Caml-list] " Vincent Hanquez
2008-02-07 16:40   ` David Teller
2008-02-07 15:17 ` Jacques Garrigue
2008-02-07 15:22   ` Jon Harrop
2008-02-08  9:54     ` Vincent Hanquez
2008-02-07 15:52   ` David Teller
2008-02-07 16:06     ` Olivier Andrieu
2008-02-07 16:23       ` David Teller
2008-02-08  9:53   ` Vincent Hanquez
2008-02-08 10:52     ` rlehy
2008-02-08 11:56       ` Vincent Hanquez
2008-02-08 12:40         ` Bünzli Daniel
2008-02-08 15:39           ` David Teller [this message]
2008-02-08 17:06             ` Eric Cooper
2008-02-08 20:02               ` David Teller
2008-02-08 19:29             ` Bünzli Daniel
2008-02-08 21:13               ` David Teller
2008-02-10 12:35           ` Vincent Hanquez
2008-02-08 19:07     ` Jon Harrop
2008-02-10 11:58       ` Vincent Hanquez
2008-02-10 16:51       ` Matthew William Cox
2008-02-07 15:33 ` Jon Harrop
2008-02-07 16:25   ` David Teller
2008-02-07 23:10 ` David Teller
2008-02-10 18:47 ` Yaron Minsky
2008-02-10 22:05   ` David Teller
2008-02-11  2:16     ` Yaron Minsky
2008-02-11  8:45       ` David Teller
2008-02-11 12:12         ` Yaron Minsky
2008-02-11 12:53           ` David Teller
2008-02-11 23:09             ` Yaron Minsky

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=1202485185.7079.18.camel@Blefuscu \
    --to=david.teller@univ-orleans.fr \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).