By Topic

The Implementation of a Persistent Type-Safe Object-Oriented Programming Language

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Sallabi, O.M. ; Garyounis Univ. Benghazi, Benghazi ; Harrison, C.

In many software development systems semantic checking is performed after the editing process and within an "edit-compile-execute" cycle. When such systems are used in a teaching role, students may construct programs, and larger-scale software systems, which contain type errors. All type errors must be corrected if the software is to execute properly and this involves a significant overhead. In the IOPL (Initial Object-Oriented Programming Language) system, incremental type checking is provided via an editor that manipulates the persistent abstract syntax representation of an application, ensuring that no syntax errors and no type errors occur during the editing process.

Published in:

Innovations in Information Technology, 2007. IIT '07. 4th International Conference on

Date of Conference:

18-20 Nov. 2007