{"title":"关于结构化编程的两个误解","authors":"P. Denning","doi":"10.1145/800181.810321","DOIUrl":null,"url":null,"abstract":"For some time I and others have been exhorting promoters of 'structured programming' to define what they mean by it. To my delight this has been happening more and more frequently. Yet, as they pen their definitions, many writers are revealing their ignorance of the basic issues to which Dahl, Dijkstra, Hoare, Knuth, Wirth and others have attempted to draw our attention when discussing 'structured programming' [11, 14, 22, 23, 30, 31]. Two misconceptions in particular have been turning up with alarming frequency.","PeriodicalId":447373,"journal":{"name":"ACM '75","volume":"100 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Two misconceptions about structured programming\",\"authors\":\"P. Denning\",\"doi\":\"10.1145/800181.810321\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"For some time I and others have been exhorting promoters of 'structured programming' to define what they mean by it. To my delight this has been happening more and more frequently. Yet, as they pen their definitions, many writers are revealing their ignorance of the basic issues to which Dahl, Dijkstra, Hoare, Knuth, Wirth and others have attempted to draw our attention when discussing 'structured programming' [11, 14, 22, 23, 30, 31]. Two misconceptions in particular have been turning up with alarming frequency.\",\"PeriodicalId\":447373,\"journal\":{\"name\":\"ACM '75\",\"volume\":\"100 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1900-01-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"ACM '75\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/800181.810321\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"ACM '75","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/800181.810321","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
For some time I and others have been exhorting promoters of 'structured programming' to define what they mean by it. To my delight this has been happening more and more frequently. Yet, as they pen their definitions, many writers are revealing their ignorance of the basic issues to which Dahl, Dijkstra, Hoare, Knuth, Wirth and others have attempted to draw our attention when discussing 'structured programming' [11, 14, 22, 23, 30, 31]. Two misconceptions in particular have been turning up with alarming frequency.