Re: why doesn't this compile ?

"Richard E Maine" <nospam@xxxxxxxxxxxxx> wrote in message
news:nospam-BF37BA.08405228042005@xxxxxxxxxxxxxxxxxxxxx

> In f2003, this is solved by dropping the keyword "module" from the
> module procedure statement. The restriction to module procedures was
> silly in the first place; the only thing important was that an explicit
> interface be accessible. Of course, the keyword "module" is still
> allowed for compatibility with existing code (and in that case, it is
> restricted to being a module procedure just because it is strange to
> have a "module procedure" statement refer to something that isn't). But
> there will probably be little reason for using the "module" keyword in
> new f2003 code except for issues of compatibility with f90/f95
> compilers; it doesn't add any useful functionality.

Why didn't you just standardize existing practice and permit
any procedure whose interface is explicit to be named as a
module procedure?

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


.

Relevant Pages

  • Re: why doesnt this compile ?
    ... in a generic interface block. ... module procedure statement. ... already explicit, but which is not a module procedure, then this is ... this is solved by dropping the keyword "module" from the ...
    (comp.lang.fortran)
  • Re: Interface declarations
    ... There are 2 things you can do with an interface block. ... have a module procedure statement, because that would not actually tell ... Some interface blocks define generics. ...
    (comp.lang.fortran)
  • Re: why doesnt this compile ?
    ... You either have an interface body or use a module procedure statement. ... If you have a procedure whose interface is already explicit, but which is not a module procedure, then this is awkward. ... "module procedure" in the main program is a compiler *extension*, ...
    (comp.lang.fortran)
  • Re: Program Fails When Parameter Fixed Constants are Changed (F77) ??
    ... manner. ... If it is contained within a module, then it is a module procedure ... the module procedure statement isn't what makes it ... gfortran emits the same error. ...
    (comp.lang.fortran)