{"title":"WG5和PL22.3联合会议报告2013年6月,荷兰代尔夫特","authors":"D. Muxworthy","doi":"10.1145/2553038.2553039","DOIUrl":null,"url":null,"abstract":"After the long hiatus in the 1980s it was decided, partly to prevent a recurrence and partly to keep more closely to ISO schedules, that future revisions of the Fortran standard should be alternately major and minor. Thus Fortran 2008 was scheduled to be minor especially as vendors were struggling to implement all of the 2003 standard before it was superseded. In the event the 2008 standard turned out to be larger than expected, mainly because the impact of coarrays had not been appreciated. During development of the standard coarrays had proved to be controversial, and there were conflicting proposals to remove them altogether, to put them in a separate part of the standard or to move all or some of the facilities to a Technical Report. In February 2008 in order to achieve consensus it was finally agreed to keep a core set of features in the main language and to develop a TR to “cater for the other features plus possibly those suggested by public comment” with the expectation that the TR would be published some three years later. Subsequently ISO renamed ‘Technical Reports’ to be ‘Technical Specifications’. Incidentally ‘consensus’ is defined by ISO to be ‘absence of sustained opposition’; it does not necessarily imply unanimity.","PeriodicalId":379614,"journal":{"name":"ACM SIGPLAN Fortran Forum","volume":"112 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2013-11-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"A report on the joint WG5 and PL22.3 meeting June 2013, Delft, Netherlands\",\"authors\":\"D. Muxworthy\",\"doi\":\"10.1145/2553038.2553039\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"After the long hiatus in the 1980s it was decided, partly to prevent a recurrence and partly to keep more closely to ISO schedules, that future revisions of the Fortran standard should be alternately major and minor. Thus Fortran 2008 was scheduled to be minor especially as vendors were struggling to implement all of the 2003 standard before it was superseded. In the event the 2008 standard turned out to be larger than expected, mainly because the impact of coarrays had not been appreciated. During development of the standard coarrays had proved to be controversial, and there were conflicting proposals to remove them altogether, to put them in a separate part of the standard or to move all or some of the facilities to a Technical Report. In February 2008 in order to achieve consensus it was finally agreed to keep a core set of features in the main language and to develop a TR to “cater for the other features plus possibly those suggested by public comment” with the expectation that the TR would be published some three years later. Subsequently ISO renamed ‘Technical Reports’ to be ‘Technical Specifications’. Incidentally ‘consensus’ is defined by ISO to be ‘absence of sustained opposition’; it does not necessarily imply unanimity.\",\"PeriodicalId\":379614,\"journal\":{\"name\":\"ACM SIGPLAN Fortran Forum\",\"volume\":\"112 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2013-11-26\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"ACM SIGPLAN Fortran Forum\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/2553038.2553039\",\"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/2553038.2553039","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A report on the joint WG5 and PL22.3 meeting June 2013, Delft, Netherlands
After the long hiatus in the 1980s it was decided, partly to prevent a recurrence and partly to keep more closely to ISO schedules, that future revisions of the Fortran standard should be alternately major and minor. Thus Fortran 2008 was scheduled to be minor especially as vendors were struggling to implement all of the 2003 standard before it was superseded. In the event the 2008 standard turned out to be larger than expected, mainly because the impact of coarrays had not been appreciated. During development of the standard coarrays had proved to be controversial, and there were conflicting proposals to remove them altogether, to put them in a separate part of the standard or to move all or some of the facilities to a Technical Report. In February 2008 in order to achieve consensus it was finally agreed to keep a core set of features in the main language and to develop a TR to “cater for the other features plus possibly those suggested by public comment” with the expectation that the TR would be published some three years later. Subsequently ISO renamed ‘Technical Reports’ to be ‘Technical Specifications’. Incidentally ‘consensus’ is defined by ISO to be ‘absence of sustained opposition’; it does not necessarily imply unanimity.