{"title":"Restructuring of APL functions","authors":"A. Arroyo","doi":"10.1145/503643.503660","DOIUrl":null,"url":null,"abstract":"The philosophy and style that has come to be known as \"structured programmlng\" emphasizes great concern with the manner in which a program is organized [1]. It implies that some program constructions are more effective than others, even though both might yield identical results. In many software applications, human efficiency (which might be related to such things as the ability to read, alter and understand programs) is more important than computer efficiency (which includes less memory space and/or execution time).In APL, branching is generally used within a defined function to direct the execution of commands. It is denoted by the symbol → followed by an expression E: →E. Since the value of E, the expression to the right of the branch arrow, may be scalar or vector, the form the branch command takes is a function of the ability of the programmer. A suitable standard form for the branch command is desirable and feasible.For the purposes of this discussion, the \"branch to specified line number or execute next line\": form of the branch command is selected as the standard form. It is entirely feasible to perform branch standardization automatically and still preserve the meaning of the original function. This paper describes such an approach.","PeriodicalId":166583,"journal":{"name":"Proceedings of the 16th annual Southeast regional conference","volume":"2016 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1978-04-13","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 16th annual Southeast regional conference","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/503643.503660","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
The philosophy and style that has come to be known as "structured programmlng" emphasizes great concern with the manner in which a program is organized [1]. It implies that some program constructions are more effective than others, even though both might yield identical results. In many software applications, human efficiency (which might be related to such things as the ability to read, alter and understand programs) is more important than computer efficiency (which includes less memory space and/or execution time).In APL, branching is generally used within a defined function to direct the execution of commands. It is denoted by the symbol → followed by an expression E: →E. Since the value of E, the expression to the right of the branch arrow, may be scalar or vector, the form the branch command takes is a function of the ability of the programmer. A suitable standard form for the branch command is desirable and feasible.For the purposes of this discussion, the "branch to specified line number or execute next line": form of the branch command is selected as the standard form. It is entirely feasible to perform branch standardization automatically and still preserve the meaning of the original function. This paper describes such an approach.