From: Dustin Sallings <dustin@spy.net>
To: Eric Stokes <eric.stokes@csun.edu>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] exception handling questions
Date: Fri, 30 Jan 2004 17:50:23 -0800 [thread overview]
Message-ID: <D5C2C9BC-538F-11D8-9D91-000393CFE6B8@spy.net> (raw)
In-Reply-To: <1B178E7D-5389-11D8-B58E-000A95A1E69A@csun.edu>
On Jan 30, 2004, at 17:02, Eric Stokes wrote:
> What about doing this.
>
> let rec 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);
> should_process fn
> ;;
>
> You may need to maintain a bit more state in various places, but it
> could work
> the way you want.
fn is a string, so feeding the same value back in wouldn't help.
The real problem here was a runtime failure in one of the functions
that is very unlikely to occur where this program is actually deployed.
I just wanted to make sure that when a failure did occur, it was dealt
with properly. The ``unknown error'' part was my biggest concern,
because I really didn't have a way to know what went wrong.
The answer to my main concern was the Printexc module:
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);
print_endline (Printexc.to_string x);
false
--
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:[~2004-01-31 1:53 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
2003-11-06 9:56 ` Richard Jones
2004-01-31 1:02 ` Eric Stokes
2004-01-31 1:50 ` Dustin Sallings [this message]
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=D5C2C9BC-538F-11D8-9D91-000393CFE6B8@spy.net \
--to=dustin@spy.net \
--cc=caml-list@inria.fr \
--cc=eric.stokes@csun.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;
as well as URLs for NNTP newsgroup(s).