Re: [Plplot-devel] Avoiding untyped variables in our Fortran binding and examples

[Alan W. I. <ir...@be...>]

P.S.

Hi Arjen:

From
<https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/346554>
it appears that you should use the /check:uninit option with the ifort
compiler to detect undefined variables.

I also see from <http://www.nag.com/nagware/np/r53_doc/nagfor.html> that
that compiler has a -C=undefined option to check for undefined
variables.

Note, I am not sure of the exact meaning of "undefined variable" in
these two references.  My hope is it simply means "undefined type",
i.e., implicit declaration, but I am not sure.  For example, some use
the term "undefined variable" when they really mean that a properly
typed variable is uninitialized.  And, of course, an uninitialized
variable is much more difficult to detect than an undefined type.

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
__________________________