From: Dustin Sallings <dustin@spy.net>
To: 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 01:50:30 -0800 [thread overview]
Message-ID: <A84885F8-103E-11D8-ADB5-000393CFE6B8@spy.net> (raw)
In-Reply-To: <20031106090201.GA9550@redhat.com>
On Nov 6, 2003, at 1:02, Richard Jones 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.
Yes, that would be nice, but I'm trying to not ask for too much. :)
As it is, I've got a function that can fail when processing large
amounts of data and it's OK to lose one as long as I know why. Right
now, the only way to know why is to rethrow:
let should_process fn =
try
(ends_with fn ".") && (is_new_enough fn) && (not (is_gzip fn))
with x ->
print_endline("Unknown error determining whether to process " ^
fn);
raise x
;;
Example output:
Unknown error determining whether to process /tmp/x/passwd.
Fatal error: exception Sys_error("/tmp/x/passwd.: Permission denied")
I'd be plenty happy to print out that message and continue, but in the
meantime, I've gotta have it abort.
--
Dustin Sallings
-------------------
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:50 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
2003-11-06 9:50 ` Dustin Sallings [this message]
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=A84885F8-103E-11D8-ADB5-000393CFE6B8@spy.net \
--to=dustin@spy.net \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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