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

Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > 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

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

On 2016-05-12 06:34- Arjen Markus wrote: [...] > My intention is to add IMPLICIT NONE anywhere where this is required: > > - At the beginning of a module, but not in the contained routines, as they > inherit that feature (the module provides the scope) > > - At the beginning of a subroutine o

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

Hi Alan, NOTE: What follows is rather specific to the Fortran language and has little to do with PLplot as such, other than that has some consequences for our Fortran binding and possibly the examples. > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > Sen

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

P.S. Hi Arjen: From it appears that you should use the /check:uninit option with the ifort compiler to detect undefined variables. I also see from

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

On 2016-05-11 09:42- Arjen Markus wrote: > I was also reminded of a small omission in the current code regarding the use of IMPLICIT NONE. It is not propagated from the module to the interface blocks. Therefore I want to add that statement everywhere where that is appropriate, just to make ext