From: William Lovas <wlovas@stwing.upenn.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] assert caught by try with _
Date: Wed, 6 Aug 2003 10:50:21 -0400 [thread overview]
Message-ID: <20030806145020.GA18143@force.stwing.upenn.edu> (raw)
In-Reply-To: <20030806121941.GC2333@roke.freak>
On Wed, Aug 06, 2003 at 02:19:41PM +0200, Michal Moskal wrote:
> On Tue, Jul 29, 2003 at 02:01:07PM -0700, Chris Hecker wrote:
> > Another way of thinking about this is that almost everybody re-#defines
> > assert in production C/C++ programs to do their own assert handling during
> > development (whether it's printing out additional information, allowing you
> > to drop into the debugger, popping up a message box, sending bug email,
> > whatever). With assert hard-coded into ocaml, you can't do this.
>
> try
> main ()
> with Assert_failure (line, col, file) -> (* or whatever it is *)
> prerr_endline "Panic! Contact support"
This won't trigger, though, if the exception has already been caught
upstream.
William
-------------------
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
next prev parent reply other threads:[~2003-08-06 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 18:34 Chris Hecker
2003-07-28 19:08 ` Nicolas Cannasse
2003-07-29 2:37 ` Chris Hecker
2003-07-29 3:17 ` Jacques Garrigue
2003-07-29 21:01 ` Chris Hecker
2003-07-30 10:22 ` Yaron M. Minsky
2003-07-30 15:47 ` james woodyatt
2003-08-06 12:19 ` Michal Moskal
2003-08-06 14:50 ` William Lovas [this message]
2003-08-06 17:44 ` Michal Moskal
2003-07-30 5:44 ` Jason Hickey
2003-07-30 5:44 ` [Caml-list] unwind-protect Jason Hickey
2003-07-30 10:30 ` Yaron M. Minsky
2003-07-30 17:29 ` Didier Remy
2003-07-31 0:47 ` Jacques Garrigue
2003-07-30 14:44 ` William Lovas
2003-07-29 22:55 [Caml-list] assert caught by try with _ Martin Berger
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=20030806145020.GA18143@force.stwing.upenn.edu \
--to=wlovas@stwing.upenn.edu \
--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).