WG5和PL22.3联合会议报告2013年6月,荷兰代尔夫特

D. Muxworthy
{"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}
引用次数: 1

摘要

在20世纪80年代的长时间中断之后,部分是为了防止这种情况再次发生,部分是为了与ISO的时间表保持更紧密的联系,Fortran标准的未来修订应该交替进行大修和小修。因此,Fortran 2008计划是次要的,特别是当供应商在2003标准被取代之前努力实现所有标准时。事实上,2008年的标准比预期的要高,主要是因为人们没有意识到天线阵的影响。在标准的发展过程中,同轴阵列被证明是有争议的,并且有相互矛盾的建议,将它们全部删除,将它们放在标准的单独部分中,或将所有或部分设备移动到技术报告中。2008年2月,为了达成共识,最终同意保留主要语言的核心功能集,并开发一个TR以“满足其他功能以及可能由公众意见建议的功能”,期望TR将在大约三年后发布。随后,ISO将“技术报告”更名为“技术规范”。顺便说一句,“共识”被ISO定义为“没有持续的反对”;它并不一定意味着全体一致。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
查看原文
分享 分享
微信好友 朋友圈 QQ好友 复制链接
本刊更多论文
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.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
期刊最新文献
Compiler Support for the Fortran 2008 and 2018 Standards The diagnostic capability of the Cray, gfortran, Intel, Nag and Oracle Fortran compilers The diagnostic capability of the Cray, gfortran, Intel, Nag and Oracle Fortran compilers Experimenting with generic programming features History of Fortran
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
0
微信
客服QQ
Book学术公众号 扫码关注我们
反馈
×
意见反馈
请填写您的意见或建议
请填写您的手机或邮箱
已复制链接
已复制链接
快去分享给好友吧!
我知道了
×
扫码分享
扫码分享
Book学术官方微信
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术
文献互助 智能选刊 最新文献 互助须知 联系我们:info@booksci.cn
Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。
Copyright © 2023 Book学术 All rights reserved.
ghs 京公网安备 11010802042870号 京ICP备2023020795号-1