Skip Navigation

The Computer Journal 1990 33(2):173-180; doi:10.1093/comjnl/33.2.173
© 1990 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 (2)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Petre, M.
Right arrow Articles by Winder, R.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

On Languages, Models and Programming Styles

M. Petre * and R. Winder *

Department of Computer Science, University College London, Gower Street, London WC1E 6BT, UK

In this paper, we attempt to clarify both the terminology used to classify programming languages and the nature of the classification itself. We feel that the current terminology and classification as captured in the literature is out of balance with the way that subject programming languages are used. We consider the accessibility of the computational model and the importance of the implementation language and suggest that a re-appraisal in this context will produce a better characterisation of both the programming language styles and their labels.


Received June 1988. revised December 1989.

* Department of Computer Science, University College London, Gower Street, London WC1E 6BT


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.