From: Doug Bagley <doug@bagley.org>
To: <caml-list@inria.fr>
Subject: Re: [Caml-list] error messages to stdout?
Date: Wed, 16 Jan 2002 13:06:28 -0600 [thread overview]
Message-ID: <15429.53044.630924.906843@ns.bagley.org> (raw)
In-Reply-To: <006001c19ebe$b2558b10$eb00a8c0@warp>
Warp wrote:
> If this message comes from RunTime ( when Dynamic Linking ) then
> that might be an exception throwed by the dynlink. Then you can
> catch it and print it to stderr ( using Printexc.to_string )
Well, I may be wrong, but this message is just printed to stdout by
toplevel/topdirs.ml ... it is not the result of an exception. And, I'm
no expert, but I believe "exceptions" already go to stderr.
The philosophy of printing all errors and diagnostics to a separate
channel from program data is, well, maybe the way to go? Just my .02
Euros.
cheers,
doug
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-01-17 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 5:12 Doug Bagley
2002-01-16 18:50 ` Warp
2002-01-16 19:06 ` Doug Bagley [this message]
2002-01-16 19:49 ` Remi VANICAT
2002-01-16 20:09 ` Doug Bagley
2002-01-17 18:33 ` John Malecki
2002-01-17 19:15 ` Doug Bagley
2002-01-19 8:11 ` Stefano Zacchiroli
2002-01-19 8:46 ` Florian Douetteau
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=15429.53044.630924.906843@ns.bagley.org \
--to=doug@bagley.org \
--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).