From: Frank Christoph <christo@nextsolution.co.jp>
To: caml-list@inria.fr
Subject: speed of byte-compiled ocaml considered high
Date: Tue, 18 Mar 1997 14:15:07 +0900 [thread overview]
Message-ID: <199703180515.OAA01112@sparc3.co.jp> (raw)
In-Reply-To: <199703152058.OAA24580@kimbark.uchicago.edu>
>>>>> "Lyn" == Lyn A Headley <laheadle@midway.uchicago.edu> writes:
> dear camlfiends, I have recently used ocaml to write a couple of
> text-munging scripts. One of them, which makes a few scans over a fairly
> large file, seems to run really fast! I was wondering if anyone has done
> any benchmarks comparing ocaml and other text-processing languages like
> perl.
I don't know if you were using the lexing or parsing facilities, but you
should be aware that, although the data tables and peripheral utilities or in
O'Caml, the engines are actually written in C and are part of the run-time
system, so they are very fast, even as bytecode. Also, I am pretty sure that
the Regexp library is based on GNU regexp, so it is also probably mostly
wrappers for C functions.
--
Frank Christoph Next Solution Co. Tel: 0424-98-1811
christo@nextsolution.co.jp Fax: 0424-98-1500
prev parent reply other threads:[~1997-03-18 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-15 20:58 Lyn A Headley
1997-03-18 5:15 ` Frank Christoph [this message]
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=199703180515.OAA01112@sparc3.co.jp \
--to=christo@nextsolution.co.jp \
--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