Skip Navigation

The Computer Journal 1967 10(3):231-243; doi:10.1093/comjnl/10.3.231
© 1967 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 (1)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Napper, R. B. E.
Right arrow Search for Related Content
Social Bookmarking
Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Some proposals for SNAP, a language with formal macro facilities

R. B. E. Napper *

Dept. of Computer Science, University of Manchester, Manchester, UK

This paper describes some proposals to apply the full power of the Compiler Compiler to an ALGOL-like base language, to provide an extendable language system that is one-pass and produces efficient object code. At its simplest SNAP permits easily defined "formal macros" which allow conventional routine calls to be coded as open sequences tailor-made to the actual parameters. The paper discusses the problems created by this facility, in particular to ensure efficient code. It finishes with an illustration of the more powerful "informal macros" which use phrase structure notation in the routine headings and Compiler Compiler instructions in the routine bodies.


* Dept. of Computer Science, University of Manchester, Manchester, 13.


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.