caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Edgar Friendly <thelema314@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Ocaml compiler features
Date: Sun, 14 Jan 2007 11:33:26 -0600	[thread overview]
Message-ID: <45AA6966.8010602@gmail.com> (raw)
In-Reply-To: <53c655920701122341l3b95328clf4e9ee40d5656dde@mail.gmail.com>

David Baelde wrote:
> > On 1/13/07, Edgar Friendly <thelema314@gmail.com> wrote:
>> >> I understand that the let statement groups the following compound
>> >> expression into one statement for the then-clause, so it's a
precedence
>> >> problem.  Would it really be enough to raise the precedence of ;
higher
>> >> than that of if/then?  Is there any reason this hasn't been done
already?
> >
> > It may be useful to note that some people might want to write code like:
> >
> > foo ;
> > x <- if y then a else b ;
> > bar ;
> >
> > In that example bar is really meant to be outside the if-then-else.
> >

I think this is the uncommon case, and deserves the parentheses:
x <- (if y then a else b) ;

> > OCaml has no such thing as statements, but only expressions. But let
> > me use these words: you want a statement-level if-then-else with lower
> > precedence than ";", it cannot be the same as this expression-level
> > if-then-else with higher precedence than ";".

I think I'm arguing that the precedence of if/then/else is too high, and
maybe should be lowered.  Of course this isn't a reasonable thing to
ask, because it'll likely break existing code.  Anyone with a way to
have my cake and eat it too?

> > If you're bored with
> > begin/end a good solution might be to define a new construct using
> > camlp4 instead of hacking the compiler. It's the good advice in
> > general for syntax problems.

Writing things in camlp4 could help me, but won't improve the world of
ocaml.  I want to compare the situation to TeX / LaTeX -- since you can
customize it so much, people fix what they don't like on their local
copy, but these improvements never make it upstream to improve the
situation for the world.

I will agree that I am too eager to "fix" the compiler, and appreciate
the community's help in tempering my inexperience.  But I'd like to help
ocaml become a better language, and this seems like a reasonable small
step to start on.

E.



  parent reply	other threads:[~2007-01-14 17:34 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13  5:37 Edgar Friendly
2007-01-13  5:56 ` [Caml-list] " Tom
2007-01-14 17:35   ` Edgar Friendly
2007-01-14 17:59     ` ketty
2007-01-14 18:21       ` Edgar Friendly
2007-01-14 18:29         ` Jon Harrop
2007-01-13  7:41 ` David Baelde
2007-01-13  9:31   ` ketty
2007-01-14 17:33   ` Edgar Friendly [this message]
2007-01-14 18:23     ` Jon Harrop
2007-01-14 18:41       ` Vincent Hanquez
2007-01-14 20:49         ` Jon Harrop
2007-01-14 23:38           ` Gabriel Kerneis
2007-01-15  0:55             ` Jon Harrop
2007-01-15  6:12               ` skaller
2007-01-15  0:05           ` Vincent Hanquez
2007-01-15  5:59             ` skaller
2007-01-15 20:23             ` Martin Jambon
2007-01-15 21:30               ` Jon Harrop
2007-01-15 22:13                 ` Try finally (was Re: [Caml-list] Ocaml compiler features) Daniel Bünzli
2007-01-15 22:27                   ` Vincent Hanquez
2007-01-15 22:40                     ` Quôc Peyrot
2007-01-15 23:08                       ` Vincent Hanquez
2007-01-15 22:17               ` [Caml-list] Ocaml compiler features Vincent Hanquez
2007-01-16  1:18                 ` skaller
2007-01-16  2:11                   ` Jon Harrop
2007-01-16  5:18                     ` Edgar Friendly
2007-01-16  6:36                       ` skaller
2007-01-16  6:33                     ` skaller
2007-01-16 13:55                     ` Brian Hurt
2007-01-16  9:00                   ` Vincent Hanquez
2007-01-16 14:14                     ` skaller
2007-01-16 15:00                       ` Vincent Hanquez
2007-01-16 17:47                         ` skaller
2007-01-16 19:24                           ` Edgar Friendly
2007-01-17  3:28                             ` skaller
2007-01-17 11:41                               ` Vincent Hanquez
2007-01-17 12:53                                 ` Olivier Andrieu
2007-01-17 13:18                                   ` Vincent Hanquez
2007-01-17 14:09                                 ` skaller
2007-01-16 19:42                           ` Jon Harrop
2007-01-16 21:15                             ` Florian Weimer
2007-01-17  3:46                             ` skaller
2007-01-17 11:50                               ` Vincent Hanquez
2007-01-15  5:56           ` skaller
2007-01-15  9:35         ` Nicolas Pouillard
2007-01-15 18:28           ` Martin Jambon
2007-01-15 19:02             ` ls-ocaml-developer-2006
2007-01-14 19:01       ` Edgar Friendly
2007-01-14 18:51     ` Vincent Hanquez
2007-01-14 20:49       ` Jon Harrop
2007-01-15  0:19         ` Vincent Hanquez
2007-01-20 19:19           ` Jon Harrop
2007-01-20 21:40             ` skaller
2007-01-14 21:47     ` Tom
2007-01-15 10:36 ` Richard Jones
2007-01-15 14:24   ` Vincent Hanquez
2007-01-16  8:45     ` Hendrik Tews
2007-01-16  9:08       ` Vincent Hanquez
2007-01-21 17:07         ` [Caml-list] native-code stack backtraces (was: Ocaml compiler features) Xavier Leroy
2007-01-21 18:53           ` Pierre Etchemaïté
2007-01-16  5:21   ` [Caml-list] Ocaml compiler features Edgar Friendly
2007-01-16  5:33     ` ketty
2007-01-16  6:00       ` Edgar Friendly
2007-01-16  6:10         ` ketty
2007-01-16  5:55     ` Christophe TROESTLER
2007-01-16 17:51       ` Edgar Friendly
2007-01-16 19:09         ` Jon Harrop
2007-01-16 19:21         ` Brian Hurt
2007-01-16 20:06         ` Jonathan Roewen
2007-01-16 20:13         ` Florian Weimer
2007-01-16  6:51     ` skaller
2007-01-16 18:01       ` Edgar Friendly
2007-01-17  2:23         ` skaller
2007-01-16  8:00   ` Florian Hars

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=45AA6966.8010602@gmail.com \
    --to=thelema314@gmail.com \
    --cc=caml-list@yquem.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).