On 2017-04-14 20:54-0700 Alan W. Irwin wrote: > To summarize, if you discovered a standards-compliant change > to our new Fortran binding implementation that would allow use of > > export FFLAGS='-O3 -std=f2003 -pedantic -Wall -Wextra' > > with gfortran, then that would allow our users/developers to at least > do minimal standards compliance checking with gfortran. But if you > feel that is too much trouble and/or the fix would obfuscate our > fortran binding code too much simply to quiet a gfortran build error > that is likely spurious, then I am content with the current > recommendation > > export FFLAGS='-O3 -Wall -Wextra' > > Of course, the (significant) downside of the current recommendation is > it means our users/developers cannot check Fortran standards > compliance with gfortran and must rely on NAG instead for such > checking.
Hi Arjen: After thinking about this some more I have become concerned that my gfortran test results are correct, and thus our code is not compliant with the pure Fortran 2003 standard nor the pure Fortran 2008 standard. For example, you could get those test results if our code is compliant with a mixture of the Fortran 2003 and Fortran 2008 standards, but with parts not compatible with pure Fortran 2003 and parts not compatible with pure Fortran 2008. For now, I would prefer to stick to pure Fortran 2003 on the principle that that standard is likely better supported by compilers than Fortran 2008. So if the NAG compiler has options equivalent to gfortran's -std=f2003 -pedantic to check compliance with the pure Fortran 2003 standard, it may reveal exactly the same issue discovered by gfortran, and that would be strong motivation for addressing that issue. By the way, the "f95" name is now obviously a misleading term describing our Fortran binding and examples. Is it time to go through our entire source tree (including documentation and build system) and replace _all_ references to "f95" (e.g., bindings/f95, examples/f95, ENABLE_f95) by the "fortran" equivalent (e.g., bindings/fortran, examples/fortran, ENABLE_fortran)? I would prefer to replace the "f95" name by "fortran" rather than "f2003" since that would allow us to move to pure Fortran 2008 compliance when the time comes without any further name changes. Alan > > Alan > __________________________ > Alan W. Irwin > > Astronomical research affiliation with Department of Physics and Astronomy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the FreeEOS equation-of-state > implementation for stellar interiors (freeeos.sf.net); the Time > Ephemerides project (timeephem.sf.net); PLplot scientific plotting > software package (plplot.sf.net); the libLASi project > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); > and the Linux Brochure Project (lbproject.sf.net). > __________________________ > > Linux-powered Science > __________________________ > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Plplot-devel mailing list > Plplot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/plplot-devel > __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
