From: Richard Jones <rich@annexia.org>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] exception handling questions
Date: Thu, 6 Nov 2003 09:02:01 +0000 [thread overview]
Message-ID: <20031106090201.GA9550@redhat.com> (raw)
In-Reply-To: <979ADAF0-1034-11D8-ADB5-000393CFE6B8@spy.net>
On Thu, Nov 06, 2003 at 12:38:27AM -0800, Dustin Sallings wrote:
>
> One thing that really seems to be missing from exception handling is
> the ability to print a stack trace from an exception. I realize
> there's a flag on the ocamlrun to print stacks for uncaught exceptions,
> but that's not exactly what I'm looking for. I'd like to be able to
> catch and exception, log it, and continue.
>
> Similarly, is there a way to print an exception at least like the
> toplevel does? I can catch any type of exception with the appropriate
> pattern, but I don't see how I can report it without expecting it.
And while we're at it, printing out a full stack trace with function
names and parameters.
Rich.
--
Richard Jones. http://www.annexia.org/ http://freshmeat.net/users/rwmj
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
"I wish more software used text based configuration files!"
-- A Windows NT user, quoted on Slashdot.
-------------------
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-11-06 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 8:38 Dustin Sallings
2003-11-06 9:02 ` Richard Jones [this message]
2003-11-06 9:50 ` Dustin Sallings
2003-11-06 9:56 ` Richard Jones
2004-01-31 1:02 ` Eric Stokes
2004-01-31 1:50 ` Dustin Sallings
2003-11-06 9:47 ` Oleg Trott
2003-11-06 10:39 ` Dustin Sallings
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=20031106090201.GA9550@redhat.com \
--to=rich@annexia.org \
--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).