Show simple item record

The Competence/Performance Dichotomy in Programming

dc.date.accessioned2004-10-01T20:36:40Z
dc.date.accessioned2018-11-24T10:10:31Z
dc.date.available2004-10-01T20:36:40Z
dc.date.available2018-11-24T10:10:31Z
dc.date.issued1977-01-01en_US
dc.identifier.urihttp://hdl.handle.net/1721.1/5775
dc.identifier.urihttp://repository.aust.edu.ng/xmlui/handle/1721.1/5775
dc.description.abstractWe consider the problem of automating some of the duties of programmers. We take as our point of departure the claim that data management has been automated to the point where the programmer concerned only about the correctness (as opposed to the efficiency) of his program need not involve himself in any aspect of the storage allocation problem. We focus on what we feel is a sensible next step, the problem of automating aspects of control. To accomplish this we propose a definition of control based on a fact/ heuristic dichotomy, a variation of Chomsky's competence/performance dichotomy. The dichotomy formalizes an idea originating with McCarthy and developed by Green, Hewitt, McDermott, Sussman, Hayes, Kowalski and others. It allows one to operate arbitrarily on the control component of a program without affecting the program's correctness, which is entirely the responsibility of the fact component. The immediate objectives of our research are to learn how to program keeping fact and control separate, and to identify those aspects of control amenable to automation.en_US
dc.format.extent18 p.en_US
dc.format.extent5144369 bytes
dc.format.extent4037011 bytes
dc.language.isoen_US
dc.titleThe Competence/Performance Dichotomy in Programmingen_US


Files in this item

FilesSizeFormatView
AIM-400.pdf4.037Mbapplication/pdfView/Open
AIM-400.ps5.144Mbapplication/postscriptView/Open

This item appears in the following Collection(s)

Show simple item record