caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vincent Aravantinos <vincent.aravantinos@yahoo.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: Gurus Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Which syntax to teach ?
Date: Tue, 30 Oct 2007 20:02:56 +0100	[thread overview]
Message-ID: <27F204A8-D45A-4CBF-84BB-BB0A23A261CA@yahoo.fr> (raw)
In-Reply-To: <1193766983.7594.15.camel@rosella.wigram>


Le 30 oct. 07 à 18:56, skaller a écrit :

> On Tue, 2007-10-30 at 12:08 -0500, Edgar Friendly wrote:
>> Brian Hurt wrote:
>>> Chung-chieh Shan wrote:
>>>
>>>> Any tips on how (and perhaps how not) to teach functors?
>
> The problem teaching functors is that the essential feature
> of functors is missing -- a functor is a structure preserving
> map but there's no way to specify any structure other than
> in comments.

Indeed, I don't really see the link between Ocaml functors and  
Category ones (???). Could someone explain this ?

Classically, types would be the objects and functions would be the  
arrows. But then a functor does not map a type to each original type  
neither a function to each original function. So what ?

Maybe we could see all the module structures associated to a module  
signature form a category ? And then a (ocaml) functor would indeed  
be a (category) functor from the category associated to the signature  
of the parameter to the category of its returned module type. (?)

Is this the way to go ? I thing I've read once that it was linked  
with "institutions" theory (of Goguen), is this right ?

Thanks for answers,
Vincent

  reply	other threads:[~2007-10-30 19:03 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 [this message]
2007-10-30 18:50           ` William D. Neumann
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=27F204A8-D45A-4CBF-84BB-BB0A23A261CA@yahoo.fr \
    --to=vincent.aravantinos@yahoo.fr \
    --cc=caml-list@inria.fr \
    --cc=skaller@users.sourceforge.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).