Identifying and correcting Java programming errors for introductory computer science students

By M. Hristova, Ananya Misra, M. Rutter, Rebecca T. Mercuri. Technical Symposium on Computer Science Education, 2003

307 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems, Software

View Paper: https://www.semanticscholar.org/paper/9133aec9cef622272d4f93805c13de9a948d4b31

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

In Information Systems

In Software

Citations in the corpus

Common logic errors made by novice programmers (2018, background): “Hristova et al. [10] found improper casting, not storing the result from a call to a non-void method, and flow reaching the end of a non-void method were among the most commonly made logic errors in Java.”
Debugging: finding, fixing and flailing, a multi-institutional study of novice debuggers (2008, methodology): “Other recent novice debugging work includes that of Hristova, Misra, Rutter, and Mercuri (2003), which identiﬁed instructor-and teaching assistant-reported novice Java syntax errors in an attempt to construct a tool to generate more meaningful error messages than those displayed by the Java…”
Studying the effect of AI Code Generators on Supporting Novice Learners in Introductory Programming (2023, unknown): “One main approach to improving the learning experience is the use of assistive programming environments, which can help alleviate misconceptions in syntax [1, 35], and conceptual knowledge [81].”
Students’ Misconceptions and Other Difficulties in Introductory Programming (2017, methodology): “…1986); language-independent conceptual bugs (Pea 1986); categorizing misconceptions by causes (Clancy 2004); using compilation error frequencies of large-scale datasets (Brown et al. 2014); syntax errors, semantic errors, and logic errors (Hristova et al. 2003; McCall and Kölling 2014); and others.”
All syntax errors are not equal (2012, methodology): “Another example in this category is the Expresso tool [3], which operates as a pre-compiler, producing detailed messages from a set of pre-deﬁned common syntax errors.”
Syntax errors just aren't natural: improving error reporting with language models (2014, methodology): “[8], but this approach is limited to predefined heuristic rules addressing a specific selection of common mistakes.”