From: "Christoph Höger" <christoph.hoeger@tu-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Segmentation fault due to uncaught type error
Date: Wed, 30 Jul 2014 17:28:05 +0200 [thread overview]
Message-ID: <53D90F05.3070109@tu-berlin.de> (raw)
In-Reply-To: <1E6C6D2A-E786-4EF5-85A0-0835A4F593F0@math.nagoya-u.ac.jp>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 30.07.2014 16:24, schrieb Jacques Garrigue:
> If there is really a bug in the compiler, this is indeed bad. This
> happens once in a while, and we fix that as soon as possible. A
> good idea would be to check with a recent version of the compiler,
> for instance the current state of the 4.02 branch, which is now
> pretty stable.
>
> svn co http://caml.inria.fr/svn/ocaml/version/4.02
I am going to give it a try. Should be a no-brainer with opam.
> Otherwise, if you know what the type error should be, you can try
> to explain it with a snippet of code. Sometimes what the type
> should be is not so clear :-)
Hmm. Basically, I am using a lense like this:
let state = { get = (fun a -> a#get_sim_state) ; set = fun a b ->
b#set_sim_state a }
In one point of the program, I am using it to get an option, in
another I (and that's the error) use it to get the record directly.
Then I feed the program with an object that delivers a option (i.e.
get_sim_state yields an option of the state record) and the
typechecker accepts that.
The program is here:
https://github.com/AMSUN-Berlin/ocsimrun/tree/typecheck_bug
The relevant bits are in sim.ml and simTests.ml (and maybe monads.ml).
I have removed all dependencies that are complicated to install. The
rest should be a simple opam install ... && oasis setup && ./configure
&& make
> And bug reports go to the bug tracking system.
> http://caml.inria.fr/mantis/ It’s better if you can cut it down to
> something understandable, but if you can’t we’ll still look into
> it.
Good to hear.
- --
Christoph Höger
Technische Universität Berlin
Fakultät IV - Elektrotechnik und Informatik
Übersetzerbau und Programmiersprachen
Sekr. TEL12-2, Ernst-Reuter-Platz 7, 10587 Berlin
Tel.: +49 (30) 314-24890
E-Mail: christoph.hoeger@tu-berlin.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlPZDwUACgkQhMBO4cVSGS/TGwCePh6rx4OI7uWnYieDjibP3Avc
cZQAoLJMQNpXYUK77fTX6TnZh5KiXMQ4
=QSvy
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-07-30 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:11 Christoph Höger
2014-07-30 14:24 ` Jacques Garrigue
2014-07-30 15:28 ` Christoph Höger [this message]
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=53D90F05.3070109@tu-berlin.de \
--to=christoph.hoeger@tu-berlin.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