From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: daniel.buenzli@epfl.ch, caml-list@inria.fr
Subject: Re: [Caml-list] How to compile different implementations of the same lib
Date: Thu, 01 Dec 2005 18:03:33 +0100 [thread overview]
Message-ID: <438F2CE5.9030105@univ-savoie.fr> (raw)
In-Reply-To: <20051201.100719.07647797.garrigue@math.nagoya-u.ac.jp>
> A result is that there cannot be any inlining between client and
> library. Actually, this is even worse than that: this also prevents
> direct function calls, as the concrete information about functions is
> also in the .cmx. All calls will have to go through closures. Just
> like when you call a function received as parameter, or inside a
> functor.
>
I you actually decide that the dependancy is for .cmx instead of .cmi in
the makefile (which is mandatory for nativecode) with proper -I option,
it should also work (maybe with a make clean when you switch
implementation) ?
May be I still do not get the problem
Anyway, there should be better support for implementation choice at link
time, because this is a nice feature of ML ...
> This suggests the other evident alternative: write the client as a
> functor. This will not be slower! But this can be more painful if
> there are several modules in the client...
>
> Jacques Garrigue
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature. The public key is
stored on www.keyserver.net
---------------------------------------------
next prev parent reply other threads:[~2005-12-01 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 9:05 Best way to choose an implementation of a lib ? Christophe Raffalli
2005-11-30 12:19 ` [Caml-list] " Jacques Garrigue
2005-11-30 14:38 ` How to compile different implementations of the same lib Daniel Bünzli
2005-11-30 16:09 ` [Caml-list] " Daniel Bünzli
2005-12-01 1:07 ` Jacques Garrigue
2005-12-01 1:53 ` malc
2005-12-01 17:03 ` Christophe Raffalli [this message]
2005-12-01 17:54 ` skaller
2005-12-01 20:09 ` Richard Jones
2005-12-01 23:47 ` skaller
2005-12-02 3:29 ` Jacques Garrigue
2005-12-01 21:33 ` Christophe Raffalli
2005-12-02 3:06 ` Jacques Garrigue
2005-11-30 16:24 ` how to detect .cmx incompatibility Stefano Zacchiroli
2005-11-30 19:48 ` [Caml-list] Best way to choose an implementation of a lib ? Eric Cooper
2005-12-01 17:05 ` Christophe Raffalli
2005-12-01 17:31 ` Eric Cooper
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=438F2CE5.9030105@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@epfl.ch \
--cc=garrigue@math.nagoya-u.ac.jp \
/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).