caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Matthias Puech <puech@cs.unibo.it>
To: caml-list@inria.fr
Subject: [Caml-list] Printexc.register_printer without catch
Date: Fri, 13 Apr 2012 11:12:27 +0200	[thread overview]
Message-ID: <4F87EDFB.6090409@cs.unibo.it> (raw)

Hello,

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?

Printexc.catch's documentation says it is deprecated and that the 
runtime system should be able to print exceptions the way they were 
registered with Printexc.register_printer, yet

# Printexc.register_printer begin function Not_found -> Some "hello" | _ 
-> None end;;
# raise Not_found;;
Exception: Not_found.

(* I would expect it to respond [Exception: hello] *)

Do I miss something here?
Thanks in advance,
     -m

             reply	other threads:[~2012-04-13  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13  9:12 Matthias Puech [this message]
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

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=4F87EDFB.6090409@cs.unibo.it \
    --to=puech@cs.unibo.it \
    --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).