From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id A19F6BBBB for ; Fri, 31 Mar 2006 22:28:01 +0200 (CEST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id k2VKS0p0001477 for ; Fri, 31 Mar 2006 22:28:01 +0200 Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id WAA30445 for ; Fri, 31 Mar 2006 22:28:00 +0200 (MET DST) Received: from mailx.valdosta.edu (mailx.valdosta.edu [168.18.130.251]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id k2VKRwD0001472 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 31 Mar 2006 22:27:59 +0200 Received: from blazemail.valdosta.edu (blazemail.valdosta.edu [168.18.130.208]) by mailx.valdosta.edu (8.13.6/8.13.6) with ESMTP id k2VKRvc8013777; Fri, 31 Mar 2006 15:27:57 -0500 (EST) (envelope-from jtbryant@valdosta.edu) Received: from chunky (chunky.valdosta.edu [168.18.160.102]) by blazemail.valdosta.edu (iPlanet Messaging Server 5.2 HotFix 2.04 (built Feb 8 2005)) with ESMTP id <0IX000JDAE6LH2@blazemail.valdosta.edu>; Fri, 31 Mar 2006 15:27:57 -0500 (EST) Date: Fri, 31 Mar 2006 15:27:34 -0500 From: Jonathan Bryant Subject: Re: FP & Software Engineering In-reply-to: To: Philippe Narbel Cc: caml-list@inria.fr Reply-To: jtbryant@valdosta.edu Message-id: <1143836854.14880.104.camel@localhost.localdomain> MIME-version: 1.0 X-Mailer: Evolution 2.6.0 Content-type: text/plain Content-transfer-encoding: 7BIT References: <1143673272.14880.31.camel@localhost.localdomain> X-PMX-Version: 5.1.2.240295, Antispam-Engine: 2.3.0.1, Antispam-Data: 2006.3.31.120608 X-Miltered: at nez-perce with ID 442D90D0.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 442D90CE.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; functor:01 hofs:01 narbel:01 hofs:01 functors:01 parametric:01 polymorphism:01 fpls:01 notation:01 ocaml:01 jfla:01 narbel:01 2006:98 wrote:01 wrote:01 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.0.3 Wow. I think I follow most of that, but ATM I do wish I spoke more than about 2 words of French. Some of the later examples I'm a little lost on, but I've only given it a cursory glance so far. While this is great for the modules, it doesn't seem as though there is a way to indicate much other than the module/functor system (although it is possible that this is due to my shortcomings in the French language :). Anything on the use of partial application, lexical scoping, HOFs, etc. as design elements? --Jonathan On Fri, 2006-03-31 at 15:11 +0200, Philippe Narbel wrote: > > > Ok. I have a question (or set of questions) that requires the expertise > > of the list, so here it goes: > > > > [...] > > > Has anybody ever come up with a way of doing these things (HOFs, > > functors, partial application, module types, parametric polymorphism) in > > UML or any kind of modeling language? If not, how are these things > > usually notated in academic settings (symbolicly, not verbally)? Is > > there anything I can make visually that qualifies? Google did not > > reveal a modeling language for FPLs, so I'm lost. > > > > > hello, > > I have been very interested in these questions for > some time now. As a matter of fact, UML is not > very good at all to represent generic architectures... > > Here in Bordeaux, I made my ML students use a special > notation which is close to Petri nets. I introduce it in > my book about OCaml, but -- as Filiatre said --, it is only > printed in french so far. > > However, you can find a paper on the internet that > I wrote for the INRIA conference JFLA'2004 about this subject. > It is also in french but the examples aren't, and you should > be able to figure out how the representation works by > looking at the figures: > > http://jfla.inria.fr/2004/actes/PS/12-narbel.ps > > of course, feel free to ask me any more questions. > > Ph. Narbel > > >