caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Remi VANICAT <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] error messages to stdout?
Date: 16 Jan 2002 20:49:04 +0100	[thread overview]
Message-ID: <87n0ze9ivj.dlv@wanadoo.fr> (raw)
In-Reply-To: <15429.3000.625598.380078@ns.bagley.org>

Doug Bagley <doug@bagley.org> writes:

> I've been learning how to use Ocaml for writing scripts, and I've
> encountered a small problem.
> 
> By "scripts", I mean they have the canonical custom toplevel in the
> interpreter line.  They also dynamically load libs.
> 
> I had updated one lib and not another that depended on it, so I got a
> message like so, to stdout:
> 
>  File /usr/local/lib/ocaml/contrib/fs_lib.cma is not up-to-date with respect to
>  interface Pcre
> 
> The problem was that I piped my ocaml script's output to a file that
> was supposed to just contain data, and then I graphed it, so the error
> message showed up in a graph, which was kind of funny but not what I
> expected. I use pipes and filters a lot, so this could really put a
> wrench in my plans.
> 
> Anyway, it would be like, cool, if I could get those errors going to
> stderr instead, or be enlightened as to the error of my
> ways. Thanks.

you should compile your program to (at least) bytecode code. It will
be faster, and those kind of error will only exist at compile time,
not at execution time...
-------------------
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


  parent reply	other threads:[~2002-01-16 19:49 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
2002-01-16 19:49 ` Remi VANICAT [this message]
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=87n0ze9ivj.dlv@wanadoo.fr \
    --to=vanicat@labri.u-bordeaux.fr \
    --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).