From: "Chris King" <colanderman@gmail.com>
To: "Zheng Li" <li@pps.jussieu.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Why thread.cmi of vmthreads/systhreads different
Date: Fri, 27 Jul 2007 11:33:59 -0400 [thread overview]
Message-ID: <875c7e070707270833j2b7f9e01m1287f3f559e0939d@mail.gmail.com> (raw)
In-Reply-To: <87bqdyw6ko.fsf@pps.jussieu.fr>
On 7/27/07, Zheng Li <li@pps.jussieu.fr> wrote:
> My point is that two different versions of thread.cmi greatly reduce the
> flexibility. I don't see many obstacles to make them agree, but I'm not sure
> whether there exist other factors to prevent that from happening.
This is a perfect example of a situation in which Piotr Wieczorek's
interface manipulation patches [1] would come in handy. In
particular, they would allow each of the implementations of the Thread
module to be retyped to a common interface, so that they can share a
.cmi.
- Chris
[1] http://caml.inria.fr/pub/ml-archives/caml-list/2006/12/c7461312202053f2213a9bb33206fcb8.en.html
prev parent reply other threads:[~2007-07-27 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 9:15 Zheng Li
2007-07-27 15:33 ` Chris King [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=875c7e070707270833j2b7f9e01m1287f3f559e0939d@mail.gmail.com \
--to=colanderman@gmail.com \
--cc=caml-list@inria.fr \
--cc=li@pps.jussieu.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;
as well as URLs for NNTP newsgroup(s).