From: Arjen M. <Arj...@de...> - 2013-10-30 07:42:04
|
Hi Alan, James, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > > Of course, the important question s why we support two styles in that sed script? I > am sure we did that deliberately with the motivation of wanting to support a wide > range of Fortran compilers. In other words we were worried that some of them might > complain about > > integer, parameter :: PL_FCI_SANS = z'0' > ... > > @Arjen: are we being too cautious here? I note from > http://gcc.gnu.org/wiki/Fortran2003 that gfortran already has almost complete support > for Fortran 2003 (and certainly the general BOZ support), and I wonder if other > fortran compilers are typically also compliant with Fortran 2003, at least to the extent > of general support for integer parameter style above for BOZ constants? > I just checked the overview regularly provided by the ACS Fortran Forum about the support for the features in the various standards by 11 different Fortran compilers and binary, octal and hexadecimal constants have been supported for quite some time now by these compilers. While I am not entirely sure this entry extends to the use in PARAMETER statements, I think we can safely assume that this is the case. My suggestion therefore is that we adjust the code and use the "integer, parameter" form exclusively. Should some one come up and complain about this, we will of course have to consider that issue, but constants should be constants in my opinion. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |