{"title":"处理输入和输出的指针","authors":"A. Markus","doi":"10.1145/3068783.3068784","DOIUrl":null,"url":null,"abstract":"Robust handling of input to a program often requires a large amount of code: parsing the input if it consists of more than just the values, checking that the input makes sense and reporting errors if it does not. For programs of an ad hoc nature or even more than ad hoc writing all that code may be too much work. So the input will often consist of little more than read statements and then some checks to see if the values make sense:","PeriodicalId":379614,"journal":{"name":"ACM SIGPLAN Fortran Forum","volume":"63 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2017-03-22","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Pointers for handling input and output\",\"authors\":\"A. Markus\",\"doi\":\"10.1145/3068783.3068784\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Robust handling of input to a program often requires a large amount of code: parsing the input if it consists of more than just the values, checking that the input makes sense and reporting errors if it does not. For programs of an ad hoc nature or even more than ad hoc writing all that code may be too much work. So the input will often consist of little more than read statements and then some checks to see if the values make sense:\",\"PeriodicalId\":379614,\"journal\":{\"name\":\"ACM SIGPLAN Fortran Forum\",\"volume\":\"63 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2017-03-22\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"ACM SIGPLAN Fortran Forum\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/3068783.3068784\",\"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 SIGPLAN Fortran Forum","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/3068783.3068784","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Robust handling of input to a program often requires a large amount of code: parsing the input if it consists of more than just the values, checking that the input makes sense and reporting errors if it does not. For programs of an ad hoc nature or even more than ad hoc writing all that code may be too much work. So the input will often consist of little more than read statements and then some checks to see if the values make sense: