caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Tom Hirschowitz <Tom.Hirschowitz@inria.fr>
To: Brian Rogoff <bpr@best.com>, caml-list@inria.fr
Subject: Re: [Caml-list] good reference on modules?
Date: Tue, 20 Mar 2001 09:32:54 +0100	[thread overview]
Message-ID: <3AB715B6.FAA36612@inria.fr> (raw)
In-Reply-To: <Pine.BSF.4.21.0103141215300.2566-100000@shell5.ba.best.com>

I liked too the three first chapters of Claudio Russo's thesis 

http://www.dcs.ed.ac.uk/home/cvr/ECS-LFCS-98-389.html

for a more abstract but very clear analysis.

I'm just reading the next ones at the moment.

Brian Rogoff a écrit :
> 
> On Wed, 14 Mar 2001, Chris Hecker wrote:
> >
> > Coming from a C++ background, my idea of a module is a text file on the hard disk.  Obviously, they're a bit more powerful than that in OCaml.  Is there a good reference (book, tutorial paper, website, whatever) that talks about modules in an in-depth way?  I've read the chapter 4 on them in the help materials, and I want more.  I was trying to understand the group example someone posted to the list a few days back, and I think I need to find a good book or something to understand the real power of modules.
> >
> > Thanks,
> 
> Some guy wrote a paper I found helpful, but the example code is in a very
> strange language that nobody uses, instead of C++ or Java.
> 
>      * A modular module system, Journal of Functional Programming 10(3),
>        2000. Full source code available in the Web appendix.
> 
> You can get it from here
> 
> http://pauillac.inria.fr/~xleroy/
> 
> -- Brian
> 
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


  reply	other threads:[~2001-03-20  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-14 20:09 Chris Hecker
2001-03-14 20:18 ` Brian Rogoff
2001-03-20  8:32   ` Tom Hirschowitz [this message]
2001-03-20 17:10     ` Brian Rogoff

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=3AB715B6.FAA36612@inria.fr \
    --to=tom.hirschowitz@inria.fr \
    --cc=bpr@best.com \
    --cc=caml-list@inria.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).