caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Poigné <poigne@gmd.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Future of labels, and ideas for library labelling
Date: Tue, 17 Apr 2001 13:53:53 +0200	[thread overview]
Message-ID: <3ADC2ED1.AD823CC3@gmd.de> (raw)

Hello

being out of office I have started to read all the contributions about
labelling and gave up halfway through. I noticed the mail by Filliatre
to which I subscribe without reservation. 

I AM A HAPPY USER OF THE CLASSIC MODE

and so far did not find it necessary to use labels. I should say that I
have written with collegues quite a lot of code as a part of the
compiler and programming system of sE (that is a language that extends
Java by synchronous programming - combining the Esterel, Lustre, and
Statecharts dialects, generating C for instance. By the way, interest
welcome). I extensively use partial evaluation for a rigorous
denotational style semantics for the synchronous sublanguage. In fact I
suspect that I could not have suceeded without partial evaluation (to
comment on another thread). In order not to loose track, a good naming
discipline is necessary (which is probably equivalent to use labels in
this context without, personal view, cluttering the code: how awful to
write ~f: if I know the argument is a function - by position and since I
tend to use names that mean something).

On the other hand, I have programmed quite a substantial gui using the
most elementary Tk-binding. What I did is to built my own little set of
Ocaml functions for hiding Tk. I admit that labels might have helped for
dealing with optional arguments, though I probably would have done the
same. 

Hence a my vote: 

- If you feel you have to add labelling keep it optional.

Axel

PS. This will be my only contribution to the subject

-- 

Dr.rer.nat. Dipl.Ing. Axel Poigne            http://ais.gmd.de/~ap 
                                             mailto:poigne@gmd.de
GMD - AiS                                    Tel: (+) 2241 142440
Schloss Birlinghoven                         Fax: (+) 2241 142324
D-53754 Sankt Augustin
Germany 

------------------------------------------------------------------
See what happened at the workshop on
"Formal Design of Safety Critical Embedded Systems" (FEmSys'01) 
   http://ais.gmd.de/~ap/femsys
-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr


             reply	other threads:[~2001-04-17 18:10 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-17 11:53 Poigné [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-11 10:48 Francois-Rene Rideau
2001-04-04 16:37 Dave Berry
2001-04-03 16:39 John R Harrison
2001-04-03  7:27 Arturo Borquez
2001-03-31  3:40 [Caml-list] Future of labels Yaron M. Minsky
2001-04-02  3:39 ` [Caml-list] Future of labels, and ideas for library labelling Jacques Garrigue
2001-04-02  7:58   ` Judicael Courant
2001-04-02  8:50     ` Markus Mottl
2001-04-02 10:33     ` kahl
2001-04-03  0:35       ` Jacques Garrigue
2001-04-03  1:36         ` Kipton M Barros
2001-04-03  1:52         ` Patrick M Doane
2001-04-03  3:53           ` Jacques Garrigue
2001-04-03  5:10             ` Patrick M Doane
2001-04-03  9:30               ` Jacques Garrigue
2001-04-03  8:52             ` Xavier Leroy
2001-04-03  9:34               ` Judicael Courant
2001-04-03  9:54               ` Jacques Garrigue
2001-04-03 12:59                 ` Jean-Christophe Filliatre
2001-04-03 14:06                   ` Jacques Garrigue
2001-04-03 14:12                     ` Daniel de Rauglaudre
2001-04-03 14:42                       ` Claude Marche
2001-04-04 19:18                     ` Gerd Stolpmann
2001-04-03  9:55               ` Ohad Rodeh
2001-04-03 12:02               ` Dave Mason
2001-04-03 13:43               ` Francois-Rene Rideau
2001-04-03 14:23                 ` Daniel de Rauglaudre
2001-04-03 13:43               ` Frank Atanassow
2001-04-03 13:58               ` Joshua D. Guttman
2001-04-03 16:52               ` Eric C. Cooper
2001-04-09  9:05                 ` John Max Skaller
2001-04-09  7:29             ` John Max Skaller
2001-04-03  8:07         ` Judicael Courant
2001-04-03  6:55     ` Chris Hecker
2001-04-09  8:11       ` John Max Skaller
2001-04-09  9:21         ` Jacques Garrigue
2001-04-09 15:06           ` Fergus Henderson
2001-04-10 18:49           ` John Max Skaller
2001-04-09 19:54         ` Chris Hecker
2001-04-10  3:37           ` Jacques Garrigue
2001-04-10  7:42             ` Judicael Courant
2001-04-10  8:25               ` Jacques Garrigue
2001-04-10  8:46               ` Claude Marche
2001-04-10 10:09                 ` Jacques Garrigue
2001-04-10 14:42                   ` Lionnel Maugis
2001-04-10  9:06             ` François-René Rideau
2001-04-11 15:34               ` Jacques Garrigue
2001-04-11 17:48                 ` Dave Mason
2001-04-10 22:43             ` Brian Rogoff
2001-04-11  8:29               ` Jacques Garrigue
2001-04-11  9:44                 ` Anton Moscal
2001-04-11 13:16                 ` Didier Remy
2001-04-11 15:11                   ` Jacques Garrigue

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=3ADC2ED1.AD823CC3@gmd.de \
    --to=poigne@gmd.de \
    --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).