From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Seeking exception source
Date: Tue, 8 Nov 2005 02:57:29 +0000 [thread overview]
Message-ID: <200511080257.30110.jon@ffconsultancy.com> (raw)
In-Reply-To: <1131416033.23991.57.camel@rosella>
Have you tried that static analyser for exceptions?
On Tuesday 08 November 2005 02:13, skaller wrote:
> Any ideas how to do that? Perhaps a camlp4 thing to instrument
> marked functions?
If you can do this then it could also be used to implement my allocation
profiling idea. I'm still learning camlp4 (I'll put up a web page on what
I've done ASAP) and I'm not up to that yet, but I think it is entirely
feasible. One problem would be the existence of many functions with the same
name.
> Although it isn't clear catching exceptions costs anything if none are
> thrown (other than code bloat)?
Non-tail recursion?
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-11-08 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 2:13 skaller
2005-11-08 2:57 ` Jon Harrop [this message]
2005-11-08 9:06 ` [Caml-list] " Nicolas Cannasse
2005-11-08 10:30 ` Alessandro Baretta
2005-11-08 10:06 ` Nicolas Cannasse
2005-11-08 10:34 ` skaller
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=200511080257.30110.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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