caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: brogoff@speakeasy.net
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] CamlP4 Revised syntax comment
Date: Tue, 29 Oct 2002 13:42:58 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0210291300540.15182-100000@grace.speakeasy.net> (raw)
In-Reply-To: <57FACEC6-EB6A-11D6-A87E-0003938819CE@inria.fr>

I agree with Gerard's comments about using the list as a ballot box 
for Revised changes, as well as his other comments. I dismissed backward 
compatibility issues as a negative in my proposal about "=", and that was 
probably too strong. It would have been better if I'd said that this 
constraint is weaker than in classic OCaml. No doubt the constraints about 
syntax changes in classic OCaml are weaker than in an ANSI or ISO standard, 
or even a standard like SML. 

There does need to be a way for Revised users to discuss aspects of the syntax 
in order that the designer (Daniel) gets some feedback. It would be more 
fruitful if contributors could provide reasons for why they favor a particular 
syntactic choice, and if they can list the negatives. One thing that always 
impressed me about some of the Ada designers was that they were quite adept 
at arguing convincingly against their own pet proposals.

I particularly like Daniel's efforts at providing justification for his 
decisions in the tutorial. One thing that's still missing is a "theory of 
what makes a good syntax for a programming language". I think it's obvious 
that such a theory would have to account for the fact that a good shell 
syntax isn't a good syntax for a more general purpose language (there 
are many more categories than just these two!) and that such a theory would 
be largely heuristic, with incompatible rules, like the principles of good 
chess play, but still useful.

-- Brian



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2002-10-29 21:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 19:02 brogoff
2002-10-25 19:25 ` Oleg
2002-10-26  9:27 ` Stefano Zacchiroli
2002-10-26 11:19   ` Daniel de Rauglaudre
2002-10-26 17:38   ` David Brown
2002-10-26 19:27     ` brogoff
2002-10-28  8:38   ` Kontra, Gergely
2002-10-28  9:28     ` Oleg
2002-10-28  9:41       ` Florian Douetteau
2002-10-28 10:04       ` Stefano Zacchiroli
2002-10-28 12:20     ` Daniel de Rauglaudre
2002-10-28 16:53       ` brogoff
2002-10-28 16:56     ` Alexander V.Voinov
2002-10-29 18:15       ` Gérard Huet
2002-10-29 18:47         ` Alexander V.Voinov
2002-10-29 20:53           ` Damien Doligez
2002-10-29 21:30             ` M E Leypold @ labnet
2002-10-29 21:42         ` brogoff [this message]
2002-10-29 11:30 ` Pierre Weis
2002-10-29 16:48   ` brogoff
2002-10-29 17:20     ` Alessandro Baretta
2002-10-30 17:49 Arturo Borquez
2002-10-31  9:21 ` Daniel de Rauglaudre

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=Pine.LNX.4.44.0210291300540.15182-100000@grace.speakeasy.net \
    --to=brogoff@speakeasy.net \
    --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).