caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "William D. Neumann" <wneumann@cs.unm.edu>
To: Edgar Friendly <thelema314@gmail.com>,
	Brian Hurt <bhurt@janestcapital.com>
Cc: caml-list@inria.fr, Chung-chieh Shan <ccshan@post.harvard.edu>
Subject: Re: [Caml-list] Re: Which syntax to teach ?
Date: Tue, 30 Oct 2007 13:50:17 -0500	[thread overview]
Message-ID: <20071030183849.M55764@cs.unm.edu> (raw)
In-Reply-To: <47276500.3050501@gmail.com>

On Tue, 30 Oct 2007 12:08:16 -0500, Edgar Friendly wrote

> That's more or less how I think of them.  Functions can be written with
> "holes" to fill in with their parameters.  In the same way, modules can
> have these "empty puzzle-spaces" that, once you fit the right kind of
> puzzle piece (module of the right type), you can plug it in (apply 
> the functor) to get a full module.

Unfortunately, on top of what one sees with HOFs, functors have a bit more 
baggage associated with learning how to use them effectively.  For one 
thing, the language is just different enough from the rest of OCaml to be a 
nuicance. And all of the extra bits needed to get the types to play nicely 
can really be hard to get a hold of (making types work as expected/desired 
seems to account for ~90% of the functor related questions to the mailing 
lists), and there's very little written up about it available for people to 
look at; section 2.4 of the manual only goes so far.

--

William D. Neumann


  parent reply	other threads:[~2007-10-30 18:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 11:36 David Teller
2007-10-24 13:18 ` [Caml-list] " Loup Vaillant
2007-10-24 13:24 ` Peng Zang
2007-10-24 13:54   ` Julien Moutinho
2007-10-24 17:23 ` Andrej Bauer
2007-10-24 19:05   ` Adrien
2007-10-25  5:14     ` Aleks Bromfield
2007-10-30 16:26     ` Chung-chieh Shan
2007-10-30 16:38       ` [Caml-list] " Brian Hurt
2007-10-30 16:59         ` Chung-chieh Shan
2007-10-30 17:08         ` [Caml-list] " Edgar Friendly
2007-10-30 17:56           ` skaller
2007-10-30 19:02             ` Vincent Aravantinos
2007-10-30 18:50           ` William D. Neumann [this message]
2007-10-30 21:45           ` Eliot Handelman
2007-10-30 18:56       ` Daniel Bünzli
2007-10-25  9:43   ` [Caml-list] " Richard Jones
2007-10-24 22:52 ` Nathaniel Gray
2007-10-24 23:10   ` Jon Harrop
2007-10-25  1:48     ` skaller
2007-10-25  2:02       ` Jon Harrop
2007-10-25  9:49       ` Richard Jones
2007-10-25 11:32         ` Stefano Zacchiroli
2007-10-25 11:52           ` Daniel Bünzli
2007-10-25 12:39           ` Richard Jones
2007-10-25 12:59         ` Michael Ekstrand
2007-10-25 13:39           ` Loup Vaillant
2007-10-25 20:32             ` Andrej Bauer
2007-10-25 22:11               ` Loup Vaillant
2007-10-25 15:14           ` Richard Jones
2007-10-25 18:47             ` Re : " Adrien
2007-11-02 16:08       ` Nathaniel Gray
2007-10-26 11:11     ` David Teller
2007-10-24 23:02 ` Jon Harrop
2007-10-26 11:09   ` David Teller

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=20071030183849.M55764@cs.unm.edu \
    --to=wneumann@cs.unm.edu \
    --cc=bhurt@janestcapital.com \
    --cc=caml-list@inria.fr \
    --cc=ccshan@post.harvard.edu \
    --cc=thelema314@gmail.com \
    /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).