Cited by 66Teaching and Learning ProgrammingSoftware Engineering ResearchLogic, programming, and type systems

Do Enhanced Compiler Error Messages Help Students?: Results Inconclusive.

Open access
Pettit, Raymond S., Homer, John, Gee, Roger·2017·Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education

Abstract

One common frustration students face when first learning to program in a compiled language is the difficulty in interpreting the compiler error messages they receive. Attempts to improve error messages have produced differing results. Two recently published papers showed conflicting results, with one showing measurable change in student behavior, and the other showing no measurable change. We conducted an experiment comparable to these two over the course of several semesters in a CS1 course. This paper presents our results in the context of previous work in this area. We improved the clarity of the compiler error messages the students receive, so that they may more readily understand their mistakes and be able to make effective corrections. Our goal was to help students better understand their syntax mistakes and, as a reasonable measure of our success, we expected to document a decrease in the number of times students made consecutive submissions with the same compilation error. By doing this, we could demonstrate that this enhancement is effective. After collecting and thoroughly analyzing our own experimental data, we found that--despite anecdotal stories, student survey responses, and instructor opinions testifying to the tool's helpfulness--enhancing compiler error messages shows no measurable benefit to students. Our results validate one of the existing studies and contradict another. We discuss some of the reasons for these results and conclude with projections for future research.

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3017680.3017768

Cites

23 of 23 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Instructors spend a considerable amount of time helping novices with cryptic error messages.

    “Instructors report that they spend a considerable amount of time helping novices with these often cryptic messages [15,31,32,37].”

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 1

  1. Christopher Watson, Frederick W. B. Li, and Jamie L. Godwin. 2012. BlueFix: using crowd-sourced feedback to support programming students in error diagnosis and repair. In Proceedings of the 11th international conference on Advances in Web-Based Learning (ICWL'12), Elvira

Cited by

Sorted by citations

Authors
Pettit, R. S., Homer, J., & Gee, R.
Affiliations
Abilene Christian University (US)
Venue
Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education
Publisher
ACM
Published
2017-03-08
Pages
465-470
OpenAlex
W2604953184
Cited by
66
References
23
Citations by year
2026: 1 · 2025: 8 · 2024: 7 · 2023: 10 · 2022: 3 · 2021: 9 · 2020: 7 · 2019: 15 · 2018: 5 · 2017: 1
FWCI
7.06
Type
conference paper
Language
en
Open access
Locations
  • ACM Technical Symposium on Computer Science Education (SIGCSE) (publishedVersion)
  • Digital Commons - ACU (Abilene Christian University) (submittedVersion, cc-by)
Topics
  • Physical Sciences › Computer Science › Computer Science Applications › Teaching and Learning Programming
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Research
  • Physical Sciences › Computer Science › Artificial Intelligence › Logic, programming, and type systems
Keywords
compiler error messages, CS1, introductory programming, syntactic errors, programming education, compilation errors, student behavior

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review