caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: michaelgrunewald@yahoo.fr (Michaël Grünewald)
To: "Bünzli Daniel" <daniel.buenzli@erratique.ch>
Cc: Andrej.Bauer@andrej.com, caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] [OSR] Exceptionless error management
Date: Fri, 01 Feb 2008 08:27:41 +0100	[thread overview]
Message-ID: <861w7xb0gi.fsf@Llea.celt.neu> (raw)
In-Reply-To: <B5C1FEA6-3C5C-4E58-8A1E-08E599BAAB93@erratique.ch> (=?iso-8859-15?Q?=22B=FCnzli?= Daniel"'s message of "Thu\, 31 Jan 2008 21\:03\:58 +0100")

Bünzli Daniel <daniel.buenzli@erratique.ch> writes:

>> time jot 1000000 | ./in.native
>
> real	0m4.814s
> user	0m4.371s
> sys	0m0.218s

You are timing `jot' aren't you?

>> time jot 1000000 | ./inb.native
>
> real	0m4.790s
> user	0m4.355s
> sys	0m0.217s

The recommendation you proposed would be even more useful if it
emphasizes when ``Exceptionless error management'' is adequate. You
can rewrite last sentence of first paragraph

  ``The following points suggest that raising exceptions to signal
    unexceptional error cases is not a good idea.''

like this:

  ``Let's enumerate situations where raising exceptions to signal
    unexceptional error cases is not a good idea.''

Maybe would you also suppress the `bad' in the first sentence, since
it is `bad' with regard to the situations you are enumerating.
-- 
Michaël


  parent reply	other threads:[~2008-02-01  7:28 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  8:55 Bünzli Daniel
2008-01-31  9:57 ` [Caml-list] " Till Varoquaux
2008-01-31 11:01   ` Bünzli Daniel
2008-01-31 14:09     ` Andrej Bauer
2008-01-31 14:16       ` Michael Ekstrand
2008-01-31 19:28         ` David Teller
2008-01-31 19:59           ` Michael Ekstrand
2008-01-31 20:05           ` blue storm
2008-01-31 20:03       ` Bünzli Daniel
2008-01-31 20:25         ` David Teller
2008-01-31 20:40           ` David Teller
2008-01-31 21:16           ` Bünzli Daniel
2008-01-31 21:31             ` David Teller
2008-01-31 21:35           ` Jon Harrop
2008-01-31 22:01           ` Christophe Raffalli
2008-02-01  7:27         ` Michaël Grünewald [this message]
2008-02-01  7:47           ` Bünzli Daniel
2008-02-01 10:50             ` Till Varoquaux
2008-02-01 11:31               ` Bünzli Daniel
2008-02-01 15:59                 ` Vincent Hanquez
2008-02-01 18:37                   ` Bünzli Daniel
2008-02-01 19:43                     ` Vincent Hanquez
2008-02-01 16:04                 ` David Allsopp
2008-02-01  8:31 ` David Teller
2008-02-01 12:19   ` Yaron Minsky
2008-02-05 10:00 ` David Teller
2008-02-05 10:12   ` Vincent Hanquez
2008-02-05 10:26     ` Bünzli Daniel
2008-02-05 11:06       ` Vincent Hanquez
2008-02-05 13:46         ` Jon Harrop
2008-02-05 11:36       ` Frédéric van der Plancke
2008-02-06  8:45       ` Michaël Grünewald
2008-02-08 13:09         ` Bünzli Daniel
2008-02-05 14:12     ` David Teller
2008-02-11  8:12 ` David Teller
2008-02-11  9:09   ` Bünzli Daniel

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=861w7xb0gi.fsf@Llea.celt.neu \
    --to=michaelgrunewald@yahoo.fr \
    --cc=Andrej.Bauer@andrej.com \
    --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).