Skip Navigation

The Computer Journal 1991 34(1):64-72; doi:10.1093/comjnl/34.1.64
© 1991 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (3)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Paakki, J.
Right arrow Search for Related Content
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Prolog in Practical Compiler Writing

J. Paakki *

Nokia Research Center, P.O. Box 156, 02101 Espoo, Finland

We discuss the experiences gained with implementing the programming language Edison in Prolog. The evaluation of Prolog in this application area is based on a comparison with two other Edison compilers, one written in Pascal (procedural approach) and the other generated using the compiler writing systems PGS and GAG (declarative approach). The crucial hindrance to applying Prolog in practical compiler writing was found to be inefficiency of the standard Prologs. Conceptually, however, Prolog was found to be quite attractive and, as a combination of the procedural and declarative approaches, a promising candidate for the basis of a special compiler writing language that is currently under development.

Received September 1989. revised April 1990.

* Nokia Research Center, P.O. Box 156, 02101 Espoo, Finland


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.