caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeff Meister <nanaki@gmail.com>
To: "Jürgen Pfitzenmaier" <pfitzen@pfitzenmaier.de>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml considered dangerous
Date: Thu, 16 Jan 2014 18:12:57 -0800	[thread overview]
Message-ID: <CAHaHOqRJa1aU+0G8z_t2Z-bSRphTv81KQ=qdpGUPDWFerkyJfg@mail.gmail.com> (raw)
In-Reply-To: <2112632769.281907.1389913202532.open-xchange@communicator.strato.de>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

I don't have time to evaluate and respond to all your points, but your
first entry under "frightening discoveries" really jumped out at me. On
line 499:

try closed_type ty with Non_closed (ty0, real) ->

The name "ty0" is a pattern capture variable, which the pattern matching
construct binds to the first argument of the caught exn value with
constructor Non_closed. It doesn't need a prior declaration... you are
declaring it right there. Surely you were simply mistaken? I find it
unbelievable that someone could write OCaml for years, even hacking on the
compiler, without understanding basic pattern matching.


On Thu, Jan 16, 2014 at 3:00 PM, Jürgen Pfitzenmaier <
pfitzen@pfitzenmaier.de> wrote:

>   Dear Ocaml users,
>  I found some serious errors in the compiler e.g. in line 28 of typing/
> includecore.ml
>  and line 499 of typing/ctype.ml of version 3.12.1.
>
>  A longer list of errors with explanations and possible fixes will be
> under
>        www.pfitzenmaier.de/ocaml-considered-dangerous.html
>
>  regards,
>  Jürgen
>
>

[-- Attachment #2: Type: text/html, Size: 1843 bytes --]

  parent reply	other threads:[~2014-01-17  2:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 23:00 Jürgen Pfitzenmaier
2014-01-16 23:27 ` Milan Stanojević
2014-01-16 23:33 ` Daniel Bünzli
2014-01-17  0:43 ` Nicolas Braud-Santoni
2014-01-20 10:07   ` Goswin von Brederlow
2014-01-17  2:12 ` Jeff Meister [this message]
2014-01-17  2:38 ` Jacques Garrigue
2014-01-17  9:01   ` Gabriel Scherer
2014-01-18  0:39   ` Jon Harrop
2014-01-18  2:22     ` Jeremy Yallop
2014-01-18  7:04       ` Gabriel Scherer
2014-01-18  9:11         ` David Allsopp
2014-01-18  9:28           ` Gabriel Scherer
2014-01-18  9:43             ` David Allsopp
2014-01-18  9:59               ` Gabriel Scherer
2014-01-19  6:09         ` oleg

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='CAHaHOqRJa1aU+0G8z_t2Z-bSRphTv81KQ=qdpGUPDWFerkyJfg@mail.gmail.com' \
    --to=nanaki@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=pfitzen@pfitzenmaier.de \
    /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).