From: "Mattias Waldau" <mattias.waldau@tacton.se>
To: <caml-list@inria.fr>
Subject: Where did the exception occur? with Not_found -> assert false
Date: Tue, 31 Oct 2000 19:50:50 +0100 [thread overview]
Message-ID: <HDEEKOMJILGEIHIMAPCDIEJIDEAA.mattias.waldau@tacton.se> (raw)
In-Reply-To: <200010311652.RAA03158@pauillac.inria.fr>
Nice idea with 'with Not_found -> assert false'.
1. But why can't the assert-information be available for all raise? wouldn't
that be the same?
2. If the we cannot include this in 'raise', how can I automate it, so that
I get the assert-behaviour if I keep the asserts, and the normal behaviour
otherwise. I normally don't deliver code with assert enabled.
/mattias
next prev parent reply other threads:[~2000-11-02 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-31 10:14 Where did the exception occur? Damien Doligez
2000-10-31 12:09 ` Mattias Waldau
2000-10-31 16:52 ` Pierre Weis
2000-10-31 18:50 ` Mattias Waldau [this message]
2000-11-02 14:53 ` Assert Ohad Rodeh
2000-11-02 18:45 ` Assert Nicolas barnier
2000-11-03 17:34 ` Assert John Max Skaller
2000-10-31 15:27 ` Where did the exception occur? CREGUT Pierre FTRD/DTL/LAN
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=HDEEKOMJILGEIHIMAPCDIEJIDEAA.mattias.waldau@tacton.se \
--to=mattias.waldau@tacton.se \
--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).