caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Piotr Wieczorek" <p.wieczorek@epf.pl>
To: "Jean-Marie Gaillourdet" <jmg@informatik.uni-kl.de>
Cc: <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Retyping module to a new signature
Date: Thu, 29 Jun 2006 11:19:24 +0200	[thread overview]
Message-ID: <005801c69b5d$1d39d130$ae5ab33e@piotrgqd2wjase> (raw)
In-Reply-To: <86804392-80E8-4968-89CC-6ECDF6DC128A@informatik.uni-kl.de>

> Hi,
>
> On 28.06.2006, at 12:49, Piotr Wieczorek wrote:
>
>> Hi!
>> I'm trying for quite a time, to make patch to Ocaml compiler which  makes 
>> possible taking a bytecompiled module and producing identical  module but 
>> conforming to a new signature.
>> I've used some code from bytepackager to calculate coercion and  copy 
>> bytecode from original module to target one.
>> It works ok. But if order of functions in target signature is  different 
>> then in source signature, calling a function may cause  not running right 
>> one, but another.
>> Can you tell me what may I be doing wrong, or wether what i'm  trying to 
>> accomplish is possible.
>>
>
> Why do you try do that in the first place? Let us assume you have a 
> module Foo which is stored in byte code file foo.cmo, which was  compiled 
> frome the file foo.ml
> - -- foo.ml --
> let foo x y= x + y
>
> let bar x = x
> - ------------
>
> If you want to constraint Foo to a module Bar which includes only the 
> first function you could use the following source:
> - -- bar.mli ----
> val foo : int -> int -> int
> - ---------------
> - -- bar.ml -----
> include Foo
> - ---------------
>
> I compiled everything with:
>
> $ ocamlc foo.ml
> $ ocamlc bar.mli
> $ ocamlc foo.cmo  bar.ml
>
> The first step is in your step eventually not necessary, because you 
> wanted to start with a binary module.
> Hope this helps.
>
> Best regards,
>   Jean-Marie

Well, imagine following situation I got program as bunch of bytecompiled 
modules. Some of them are third-party libraries. Thereis new version of 
library released with compatible but not necessary identical signatures.
I want now to have module with identical name as source module but 
consistent with new signature.
Using Your method, I think, I cannot use the name name of new module as of 
the source module.

Piotr Wieczorek


------------------------------------------------------------------------
CIEP?E KRAJE - CIEP?E MORZA. Szukasz atrakcyjnego wypoczynku w przyst?pnej cenie, zapoznaj si? z nasz? ofert?.
ZAPRASZAMY

www.skarpatravel.pl


  reply	other threads:[~2006-06-29  9:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 10:49 Piotr Wieczorek
2006-06-28 15:45 ` [Caml-list] " Jean-Marie Gaillourdet
2006-06-29  9:19   ` Piotr Wieczorek [this message]
2006-06-29  9:20     ` Jean-Marie Gaillourdet

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='005801c69b5d$1d39d130$ae5ab33e@piotrgqd2wjase' \
    --to=p.wieczorek@epf.pl \
    --cc=caml-list@yquem.inria.fr \
    --cc=jmg@informatik.uni-kl.de \
    /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).