Re: IMPLICIT NONE (F2k8+/-)



"Gary L. Scott" <garyscott@xxxxxxx> wrote in message
news:11ln80341kkhtbd@xxxxxxxxxxxxxxxxxxxxx

> IMPLICIT NONE should finally be made default beginning at F2k8.
> Compiler switches can be specified to get the older behavior. There is
> absolutely no good reason to continue this way.

But isn't it already as of f90? I mean to say that in f90
programming, almost all the code is in modules, and typically
one puts an implicit none statement after all the use
statements in the module. All the module procedures accordingly
inherit the implicit none state from their host module which
must be overridden with implicit statements in each module
procedure if (as is sometimes the case) implicit typing is
actually desired for the given procedure.

--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end


.



Relevant Pages

  • IMPLICIT NONE (F2k8+/-)
    ... IMPLICIT NONE should finally be made default beginning at F2k8. ... Compiler switches can be specified to get the older behavior. ... There is absolutely no good reason to continue this way. ...
    (comp.lang.fortran)
  • Re: optional routine arguments
    ... first new f90 features tried. ... which used IMPLICIT ANY instead of IMPLICIT NONE. ... like the f90 form of optional arguments but doesn't support implicit ... That old Sun compiler was one of the ones I was specifically thinking ...
    (comp.lang.fortran)
  • Re: IMPLICIT NONE (F2k8+/-)
    ... Gary L. Scott wrote: ... > IMPLICIT NONE should finally be made default beginning at F2k8. ... > Compiler switches can be specified to get the older behavior. ...
    (comp.lang.fortran)
  • Re: optional routine arguments
    ... first new f90 features tried. ... that were not standardized until f90, ... Failing to have an explicit interface (which modules give you ... generally avoid implicit none, that the problems of implicit typing are ...
    (comp.lang.fortran)
  • Re: Problem when creating a.out and -convert big_endian compiler option
    ... was *not* standardized until F90, ... As a substitute, in my early f77 codes I used to use something ... implicit character*1 ...
    (comp.lang.fortran)