From: Arjen M. <Arj...@de...> - 2016-05-12 09:42:22
|
Hi Alan, > -----Original Message----- > From: Alan W. Irwin [mailto:ir...@be...] > Sent: Thursday, May 12, 2016 11:30 AM > Thanks for clearing up that nomenclature. It appears then, that the ifort and NAG > fortran compiler options I found concerned the wrong problem (undefined variable). > What we need instead is a check of our Fortran binding and Fortran examples code > for any variable without an explicit declaration, i.e., the easier problem. Presumably, > if you put "implicit none" in all the right places, it should detect any such issues, but > finding all those right places strikes me as an error-prone process so to double- > check that I hope you are able to find and use a compiler option to check for > variables that are not explicitly declared for either the ifort or NAG Fortran compilers. > As far as I can tell, gfortran does not have such an option. > For Intel Fortran the option is /warn:declarations (on Windows) or -warn:declaration (on Linux/OSX). Gfortran does have such an option: -Wimplicit, but I guess -Wall will enable it as well. According to the documentation the NAG compiler uses the option -u for this. (Key to these morsels of wisdom: "implicit"). So this issue is indeed covered. 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. |