From: Doug Bagley <doug@bagley.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] error messages to stdout?
Date: Wed, 16 Jan 2002 14:09:48 -0600 [thread overview]
Message-ID: <15429.56844.510694.554970@ns.bagley.org> (raw)
In-Reply-To: <87n0ze9ivj.dlv@wanadoo.fr>
Remi VANICAT wrote:
> 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...
Well, I certainly could do that, but I was hoping to use Ocaml to
replace my bash/awk/sed/perl scripts. For me, the convenience of
having one single source file, and no compilation step, is one of the
attractions of "scripts". As far as I can tell, the extra load time
due to compilation of the script is negligible, and I assume the
run-time is equivalent to a pre-compiled byte-code executable? I have
many scripts that do filtering, so having a clean output stream is
important to me. It seems to me that if the ability to use a custom
toplevel as a script interpreter exists, then it would be very nice if
it printed all diagnostics to stderr.
Anyway, I have a workaround, I wrote a "trampoline" program that can
be used in place of the toplevel interpreter and does the compilation
transparently for lazy persons such as myself.
It essentially turns any compiled language into a scripting language.
If anyone is interested in it ... I could clean it up for public
consumption.
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
2002-01-16 19:49 ` Remi VANICAT
2002-01-16 20:09 ` Doug Bagley [this message]
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.56844.510694.554970@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