From: "Mike Lin" <mikelin@mit.edu>
To: "Caml List" <caml-list@inria.fr>
Subject: Re: [caml-list] If OCaml were a car
Date: Sun, 19 Aug 2007 14:15:48 -0400 [thread overview]
Message-ID: <2a1a1a0c0708191115r2fba44b9y3b5478846b2a144b@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Aug 19, 10:46 am, John Carr <j...@MIT.EDU> wrote:
> OCaml has a badly designed syntax processed by a badly implemented
> parser feeding into a backend that generates poor error messages.
> All this makes the language hard to use.
I think the bad error messages break down into two categories most of the
time, 1) lengthy, unintelligible type mismatches and 2) unhelpful
(location-wise) complaints about parentheses in nested expressions. I find
that ocaml+twt helps immensely with the latter category. Basically, I'm much
much happier with the language since doing TWT - I don't have to pull my
hair out fixing things that are obvious from the indentation anyway. And,
mostly just to make a point, it does away with the fugly ;;
It's been a while since PL class so I'm not sure what can be done to make
type mismatch errors more helpful.
[-- Attachment #2: Type: text/html, Size: 935 bytes --]
next reply other threads:[~2007-08-19 18:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 18:15 Mike Lin [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-18 19:21 Richard Jones
2007-08-18 20:24 ` [Caml-list] " Jeff Meister
2007-08-18 21:32 ` Michael Vanier
2007-08-19 11:50 ` Daniel Bünzli
2007-08-19 11:59 ` Erik de Castro Lopo
2007-08-22 5:50 ` Luca de Alfaro
2007-08-22 8:13 ` Jon Harrop
2007-08-22 9:20 ` Jacques Garrigue
2007-08-24 2:54 ` Nathaniel Gray
2007-08-25 19:45 ` Oliver Bandel
2007-08-19 14:43 ` John Carr
2007-08-19 16:22 ` brogoff
2007-08-19 17:07 ` Richard Jones
2007-08-19 17:19 ` Stefano Zacchiroli
2007-08-22 6:04 ` Luca de Alfaro
2007-08-19 20:51 ` Vincent Hanquez
2007-08-21 8:05 ` David Allsopp
2007-08-21 18:33 ` Richard Jones
2007-08-19 20:30 ` Tom
2007-08-19 21:45 ` skaller
2007-08-20 3:37 ` Jon Harrop
2007-08-20 6:26 ` skaller
2007-08-20 10:00 ` Joerg van den Hoff
2007-08-21 12:03 ` Florian Hars
2007-08-20 6:54 ` skaller
2007-08-20 19:54 ` Oliver Bandel
2007-08-20 20:27 ` David Allsopp
2007-08-20 20:50 ` Ulf Wiger (TN/EAB)
2007-08-21 10:56 ` Joerg van den Hoff
2007-08-20 21:13 ` Oliver Bandel
2007-08-21 0:47 ` skaller
2007-08-21 9:51 ` Oliver Bandel
2007-08-21 10:30 ` skaller
2007-08-21 18:57 ` Richard Jones
2007-08-22 2:49 ` skaller
2007-08-22 11:33 ` Thomas Fischbacher
2007-08-21 15:48 ` brogoff
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=2a1a1a0c0708191115r2fba44b9y3b5478846b2a144b@mail.gmail.com \
--to=mikelin@mit.edu \
--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