From: skaller <skaller@ozemail.com.au>
To: John J Lee <jjl@pobox.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Executable size?
Date: 16 Nov 2003 00:41:38 +1100 [thread overview]
Message-ID: <1068903697.25869.101.camel@pelican> (raw)
In-Reply-To: <Pine.LNX.4.58.0311131923420.598@alice>
On Fri, 2003-11-14 at 06:58, John J Lee wrote:
> On Thu, 13 Nov 2003, Eric Dahlman wrote:
>
> OK. Getting back to the original question again (how to reduce data to be
> transferred over the network), both O'Caml and C statically link this
> runtime stuff, right? So, why is O'Caml's "hello world" (compressed) 45k,
> to C's 1 or 2k? Is that 43k the garbage collector? Or is it mostly that
> O'Caml, in contrast to C, is linking in a bunch of stuff from its standard
> library that isn't strictly required for "hello world"? Or something else
> again??
>
> Hope I'm not going round in circles here...
The Ocaml equivalent of a C stub program which dynamically
links to the C run time is bytecode.
Ocaml native code compiler, at least on the x86,
does not generate relocatable code, and so Ocaml
library functions cannot be dynamically linked.
[At present .. :]
In my opinion, you best bet is to generate bytecode
and distribute that. Your clients WILL have to download
the bigger ocamlrun driver harness, but hopefully
only once.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-11-15 14:42 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 16:14 John J Lee
2003-11-12 17:33 ` Richard Jones
2003-11-12 18:06 ` Dustin Sallings
2003-11-12 18:31 ` Sven Luther
2003-11-12 18:50 ` John J Lee
2003-11-13 9:10 ` Sven Luther
2003-11-13 13:46 ` John J Lee
2003-11-13 14:28 ` Sven Luther
2003-11-12 18:21 ` John J Lee
2003-11-12 22:53 ` Richard Jones
2003-11-12 23:50 ` John J Lee
2003-11-15 12:48 ` skaller
2003-11-15 15:25 ` John J Lee
2003-11-12 19:06 ` Brian Hurt
2003-11-12 18:38 ` Sven Luther
2003-11-12 19:04 ` Karl Zilles
2003-11-12 21:29 ` Brian Hurt
2003-11-12 20:03 ` Brian Hurt
2003-11-13 4:14 ` Kamil Shakirov
2003-11-13 9:06 ` Richard Jones
2003-11-13 9:18 ` Sven Luther
2003-11-12 18:46 ` John J Lee
2003-11-12 20:40 ` Brian Hurt
2003-11-12 20:10 ` Basile Starynkevitch
2003-11-12 20:35 ` John J Lee
2003-11-12 21:51 ` Brian Hurt
2003-11-12 21:35 ` David Brown
2003-11-12 22:12 ` Eric Dahlman
2003-11-12 23:32 ` Brian Hurt
2003-11-12 22:53 ` Eric Dahlman
2003-11-12 23:35 ` John J Lee
2003-11-12 23:44 ` John J Lee
2003-11-13 0:26 ` Karl Zilles
2003-11-13 1:29 ` [Caml-list] F-sharp (was: Executable size?) Oleg Trott
2003-11-14 6:04 ` [Caml-list] float_of_num Christophe Raffalli
2003-11-13 15:43 ` [Caml-list] Executable size? Eric Dahlman
2003-11-13 19:58 ` John J Lee
2003-11-13 20:36 ` Eric Dahlman
2003-11-13 22:16 ` John J Lee
2003-11-15 13:41 ` skaller [this message]
2003-11-15 15:13 ` John J Lee
2003-11-15 18:07 ` skaller
2003-11-15 13:36 ` skaller
2003-11-15 15:01 ` John J Lee
2003-11-15 17:53 ` skaller
2003-11-13 13:37 ` Florian Hars
2003-11-12 18:05 ` Dustin Sallings
2003-11-12 18:36 ` John J Lee
2003-11-12 19:04 ` Dustin Sallings
2003-11-12 20:17 ` John J Lee
2003-11-12 20:01 ` Vitaly Lugovsky
2003-11-13 1:23 ` Nicolas Cannasse
2003-11-15 12:09 ` skaller
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=1068903697.25869.101.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=jjl@pobox.com \
/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