Browse Prior Art Database

Depicting Run-Time Errors for Interpreted Programming Languages Using Threaded-Code

IP.com Disclosure Number: IPCOM000062358D
Original Publication Date: 1986-Nov-01
Included in the Prior Art Database: 2005-Mar-09
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Hintz, TE: AUTHOR

Abstract

By using threaded-code for both execution of a program and de-compiling, the operation which causes a run-time error in a statement may be precisely identified to a programmer as an aid in debugging programs written in interpreted programming languages. A great deal of time is required to correct errors in computer programs. The process of identifying and correcting errors in programs is referred to as "debugging". Many debugging utilities will detect a run-time error in a program and display an error message identifying the type of error detected. It is then necessary to carefully review the program code to discover the actual error. More recently, debugging utilities have been developed which will not only display an error message but will also indicate the location in the code where the error occurred.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 85% of the total text.

Page 1 of 1

Depicting Run-Time Errors for Interpreted Programming Languages Using Threaded-Code

By using threaded-code for both execution of a program and de-compiling, the operation which causes a run-time error in a statement may be precisely identified to a programmer as an aid in debugging programs written in interpreted programming languages. A great deal of time is required to correct errors in computer programs. The process of identifying and correcting errors in programs is referred to as "debugging". Many debugging utilities will detect a run-time error in a program and display an error message identifying the type of error detected. It is then necessary to carefully review the program code to discover the actual error. More recently, debugging utilities have been developed which will not only display an error message but will also indicate the location in the code where the error occurred. Even so, the message can often be ambiguous and not easily or correctly understood for the indicated line of code. This problem is solved by using threaded-code for both execution of a program written in an interpreted programming language and de- compiling (creating original source code). In this way, the operation which causes a run-time error in a statement is precisely known. When the statement is de-compiled to present the programmer which statement the error occurred on, the source text corresponding to the actual operation causing the error can be uniquely identified and d...