For many years, the "web home" of ISO/IEC JTC1/SC22/WG5 (the international Fortran standards committee, or WG5 for short) has been graciously hosted by NAG. I am pleased to announce that WG5 now has its own web site: https://wg5-fortran.org/ The site is served over https and is "mobile friendly".
The WG5 web site is where you'll find news about what's happening with the Fortran standard, and links to all WG5 documents. Information on current and past standards is also available there.
On the home page you will see a link to a survey, requesting opinions on and suggestions for features that you would like to see in the next Fortran standard, tentatively titled Fortran 2020. If you want to help shape the future of Fortran, please take a few minutes and fill out the survey. While the survey will remain open through January 2018, we will start analyzing responses at the October J3 meeting. Also, the list of features the survey asks you to rank may be amended based on suggestions received.
I welcome all comments on the web site, and especially if you discover any problems. Not yet done are the email list indexes and news older than 2016.
Thanks for the link.
Where would be a good place to ask you questions about the Fortran 2020 draft?
4.3.3, page 31, what is the reasoning behind:
Fortran 2008 permitted a pure statement function to reference a volatile variable, and permitted a local variable of a pure subprogram or of a BLOCK construct within a pure subprogram to be volatile (provided it was not used); this document does not permit that.
There are three image execution states: active, stopped, and failed. An image that has initiated normal termination of execution is a stopped image. An image that has ceased participating in program execution but has not initiated termination is a failed image. All other images are active images.
Isn't there a forth state: In the process of becoming active (prior to image load and any RTL initialization)
Jim, you must mean the Fortran 2015 draft. There is no F2020 draft yet!
Re: 4.3.3 - access to volatile variables are considered side-effects and pure procedures can't have side-effects.
Re: 5.3.6 - I am not an expert on this aspect of the standard, but keep in mind that nothing starts executing until all images become active, so there's no way to detect a "in process of activation" state.
If you have further questions about the standard, or are generally interested in the language, you could post in the comp.lang.fortran newsgroup and/or subscribe to the COMP-FORTRAN-90 email list at http://www.jiscmail.ac.uk/ There are several committee members who participate in both places.
No words can describe how great it is to find WG5 Fortran group have its own dedicated website and to contemplate all the communication channels this can open up over time - starting with your survey - for all the regular users of Fortran.
Fortran truly enters the modern era!
For the Fortranners out there Steve, "this is the beginning of a beautiful" thing!