From: Christian Haack <haack@macs.hw.ac.uk>
To: ultra@macs.hw.ac.uk, DSG Login <dsg@macs.hw.ac.uk>,
<church-announce@church-project.org>, <amast@cs.utwente.nl>,
<caml-list@inria.fr>, <comp-lang-ml@cs.cmu.edu>,
<compilers@iecc.com>, <eapls@jiscmail.ac.uk>,
<haskell@haskell.org>, <types@cis.upenn.edu>,
<unification@sics.se>
Subject: [Caml-list] Web Demonstration of Type Error Slicing
Date: Mon, 25 Nov 2002 12:25:45 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.44.0211251216220.1616-100000@lxultra2> (raw)
Previous methods have generally identified the location of a type
error as a particular program point or the program subtree rooted at
that point. In the paper "Type Error Slicing in Implicitly Typed
Higher-Order Languages" by two of us (Haack and Wells), we present a
new approach that treats the location of a type error as a minimal set
of program points which are necessary for the type error and presents
this "location" as a slice of the program. Connected to this paper,
we have implemented type error slicing for a subset of core Standard
ML.
We have prepared a web interface that allows you to experiment with
our implementation using just your web browser. This interface is now
available at:
http://www.cee.hw.ac.uk/ultra/compositional-analysis/type-error-slicing/
--
Sebastien Carlier, Christian Haack, and Joe Wells
Members of the ULTRA group and the Church Project
-------------------
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
next reply other threads:[~2002-11-25 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 12:25 Christian Haack [this message]
2002-11-25 15:22 ` [Caml-list] " Greg Michaelson
2002-11-25 15:26 ` Greg Michaelson
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.0211251216220.1616-100000@lxultra2 \
--to=haack@macs.hw.ac.uk \
--cc=amast@cs.utwente.nl \
--cc=caml-list@inria.fr \
--cc=church-announce@church-project.org \
--cc=comp-lang-ml@cs.cmu.edu \
--cc=compilers@iecc.com \
--cc=dsg@macs.hw.ac.uk \
--cc=eapls@jiscmail.ac.uk \
--cc=haskell@haskell.org \
--cc=types@cis.upenn.edu \
--cc=ultra@macs.hw.ac.uk \
--cc=unification@sics.se \
/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).