From: Mark Shinwell <mshinwell@janestreet.com>
To: Matthias Puech <puech@cs.unibo.it>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Printexc.register_printer without catch
Date: Fri, 13 Apr 2012 10:33:18 +0100 [thread overview]
Message-ID: <20120413093318.GA11194@janestreet.com> (raw)
In-Reply-To: <4F87EDFB.6090409@cs.unibo.it>
On Fri, Apr 13, 2012 at 11:12:27AM +0200, Matthias Puech wrote:
> Is there a way to change printing of uncaught exceptions in the
> toplevel and in (native/bytecode, 3.12) compiled code without
> wrapping the whole code in a try ... with or in Printexc.catch?
I don't believe so. However, I have nearly finished a patch to enable this, so
the feature may appear soon if I can get sufficient buy-in from the other
developers.
Mark
prev parent reply other threads:[~2012-04-13 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 9:12 Matthias Puech
2012-04-13 9:18 ` Gabriel Scherer
2012-04-13 9:43 ` Matthias Puech
2012-04-13 9:52 ` Jérémie Dimino
2012-04-13 14:04 ` Matthias Puech
2012-04-13 9:33 ` Mark Shinwell [this message]
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=20120413093318.GA11194@janestreet.com \
--to=mshinwell@janestreet.com \
--cc=caml-list@inria.fr \
--cc=puech@cs.unibo.it \
/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).