See this document in CiteSeerX!

How Do People Check Polymorphic Types? (2000)  (Make Corrections)  (5 citations)
Yang Jun, Greg Michaelson, Phil Trinder



  Home/Search   Context   Related

 
View or download:
ppig.org/workshops/../p...12thyang.pdf
Cached:  PS.gz  PS  PDF   Image  Update  Help

From:  ppig.org/worksho...12thprogramme (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: Polymorphic typechecking algorithms efficiently locate type errors in programs, but users find error reporting from such algorithms hard to comprehend. We are investigating the development of a new polymorphic type checker that reports type errors in a more understandable form. Here we present the results of experiments into human checking of both correct and incorrect polymorphic typed programs, and briefly discuss their implications for our proposed new checker. Introduction Polymorphic... (Update)

Context of citations to this paper:   More

...reproduce large amounts of counter intuitive mechanical inference. This includes reporting with arti cially introduced type variables [15]. 5. Source based. The user need not know anything of the compiler internals to understand the error message. For example error reports...

...understandable, especially by novices. To that end, we conducted the following experiment to identify human strategies in explaining types[22][21] 3.2 Characterising Human Type Explanations In comparison with the W algorithm, in our experience people appear to be far less...

Cited by:   More
Improving Polymorphic Type Explanations - Yang (2001)   (Correct)
Improving Polymorphic Type Error Reporting - Yang, Michaelson, Trinder, Wells (2000)   (Correct)
Compositional Explanation of Types and Algorithmic Debugging of.. - Chitil (2001)   (Correct)

Similar documents (at the sentence level):
11.8%:   Explaining Polymorphic Types - Jun, Michaelson, Trinder (2001)   (Correct)

Similar documents based on text:   More   All
1.1:   In A.F. Blackwell E. Bilotta (Eds). Proc. PPIG 12 Pages 171-180 .. - Th Workshop Of   (Correct)
0.6:   In G. Kadoda (Ed). Proc. PPIG 13 Pages 191-204 13 - Th Workshop Of   (Correct)
0.6:   In G. Kadoda (Ed). Proc. PPIG 13 Pages 105-111 13 - Th Workshop Of   (Correct)

Related documents from co-citation:   More   All
5:   Finding the source of type errors (context) - Wand - 1986
5:   Explaining type errors in polymorphic languages - Beaven, Stansifer - 1994
5:   Debugging type errors - Bernstein, Stark - 1995

BibTeX entry:   (Update)

Jun Yang, Greg Michaelson, and Phil Trinder. How do people check polymorphic types? In Alan F. Blackwell and Eleonora Bilotta, editors, Twelfth Annual Meeting of the Psychology of Programming Interest Group Proceedings, pages 67-77. Memoria, April 2000. http://citeseer.ist.psu.edu/jun00how.html   More

@misc{ yang00how,
  author = "J. Yang and G. Michaelson and P. Trinder",
  title = "How do people check polymorphic types",
  text = "Jun Yang, Greg Michaelson, and Phil Trinder. How do people check polymorphic
    types? In Alan F. Blackwell and Eleonora Bilotta, editors, Twelfth Annual
    Meeting of the Psychology of Programming Interest Group Proceedings, pages
    67-77. Memoria, April 2000.",
  year = "2000",
  url = "citeseer.ist.psu.edu/jun00how.html" }
Citations not processed or no citations identified.



The graph only includes citing articles where the year of publication is known.


Documents on the same site (http://www.ppig.org/workshops/12th-programme.html):   More
Experiences with Novices: The Importance of Graphical.. - George (2000)   (Correct)
How a Visualization Tool Can Be Used - Evaluating a Tool.. - Lattu, Tarhio, Meisalo (2000)   (Correct)
Uncovering Effects of Programming Paradigms: Errors in Two.. - Tukiainen (2000)   (Correct)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC