From: Didier Remy <Didier.Remy@inria.fr>
To: Martin Chabr <martin_chabr@yahoo.de>
Cc: Stephen Brackin <stephen.brackin@verizon.net>, caml-list@yquem.inria.fr
Subject: Re: Ant: [Caml-list] Duplicate functionality?
Date: Tue, 25 Oct 2005 18:25:48 +0200 [thread overview]
Message-ID: <20051025162539.GA18326@arbois.inria.fr> (raw)
In-Reply-To: <20051024031424.56990.qmail@web26803.mail.ukl.yahoo.com>
And also
http://pauillac.inria.fr/~remy/cours/appsem/
http://pauillac.inria.fr/~remy/cours/appsem/ocaml-mixins.html
or...
http://caml.inria.fr//cgi-bin/search.en.cgi?words=overlapping+objects+modules
Didier
prev parent reply other threads:[~2005-10-25 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 1:04 Stephen Brackin
2005-10-22 3:31 ` [Caml-list] " Jon Harrop
2005-10-22 5:57 ` Matt Gushee
2005-10-22 8:47 ` Gerd Stolpmann
2005-10-22 5:49 ` Jacques Garrigue
2005-10-22 10:07 ` Lauri Alanko
2005-10-22 21:12 ` Brian Hurt
2005-10-24 3:14 ` Ant: " Martin Chabr
2005-10-25 16:25 ` Didier Remy [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=20051025162539.GA18326@arbois.inria.fr \
--to=didier.remy@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=martin_chabr@yahoo.de \
--cc=stephen.brackin@verizon.net \
/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).