From: Alessandro Baretta <a.baretta@barettadeit.com>
To: Eric Cooper <ecc@cmu.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Private exceptions
Date: Wed, 01 Feb 2006 18:21:00 +0100 [thread overview]
Message-ID: <43E0EDFC.8010803@barettadeit.com> (raw)
In-Reply-To: <20060201163640.GB20172@localhost>
Eric Cooper wrote:
> On Mon, Jan 30, 2006 at 03:31:56PM +0100, Alessandro Baretta wrote:
>
> But the ability to match any exception (and re-raise it, without
> knowing anything more about it) is essential for implementing
> constructs like "unwind-protect", "with-open-file", suspend/force,
> etc.
You are right, I must admit. Yet the problem remains. There are times when
catching exceptions is unsafe. In my case, the exception aborts a database
transaction. If the exception is not propagated to the calling transaction
manager call, this will continue to execute the current transaction outside of
the transaction block--as a rollback has already been issued.
Now, of course there is never only one way to solve a given programming problem,
and I did solve mine without tampering with the exception system too
much--except that I no longer export the exception signalling a transaction
rollback, so that at least it cannot be *explicitely* filtered.
Alex
--
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL
tel. +39 02 370 111 55
fax. +39 02 370 111 54
Our technology:
The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/>
The FreerP Project
<http://www.freerp.org/>
prev parent reply other threads:[~2006-02-01 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 14:31 Alessandro Baretta
2006-02-01 16:36 ` [Caml-list] " Eric Cooper
2006-02-01 17:21 ` Alessandro Baretta [this message]
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=43E0EDFC.8010803@barettadeit.com \
--to=a.baretta@barettadeit.com \
--cc=caml-list@yquem.inria.fr \
--cc=ecc@cmu.edu \
/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