From: "Mr. Herr" <misterherr@freenet.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Simple exception - different behaviour between toplevel and compiled
Date: Wed, 19 Aug 2015 13:22:10 +0200 [thread overview]
Message-ID: <55D466E2.9090801@freenet.de> (raw)
In-Reply-To: <20150819131641.Horde.Nppwxhc-_C7qHtuTW_qqDb7@webmail.in-berlin.de>
On 19.08.2015 13:16, Oliver Bandel wrote:
> Hello,
>
>
> maybe the problem is, that the one type is a curried int * int.
> In the compiled version there seems no way to print it's contents?
> But the toplevel does print the exception clearly with the containing int * int.
> Can the toplevel's verbosity be made available in the compiled version?
>
> Ciao,
> Oliver
>
>
see the answers by Arthur 02:06h, and by gasche 07:35h with an explicit example.
next prev parent reply other threads:[~2015-08-19 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 22:41 Oliver Bandel
2015-08-18 23:32 ` David Allsopp
2015-08-19 0:06 ` Arthur Wendling
2015-08-19 5:35 ` Gabriel Scherer
2015-08-19 11:53 ` Oliver Bandel
2015-08-19 11:16 ` Oliver Bandel
2015-08-19 11:22 ` Mr. Herr [this message]
2015-08-19 11:26 ` Oliver Bandel
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=55D466E2.9090801@freenet.de \
--to=misterherr@freenet.de \
--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