Re: public/private and overloaded operator

mrestelli@xxxxxxxxx <mrestelli@xxxxxxxxx> wrote:

fortcom: Error: fquest.f90, line 33: This dummy argument of this
module procedure is of a type that has PRIVATE accessibility and the
procedure has a generic identifier that has PUBLIC accessiblity.

There were a bunch of restrictions like this that were removed with one
of the Fortran revisions. I think it was between f95 and f2003. So in
some sense, both compilers are right. You might want to look at the
particular compiler options for controlling the version of the standard
that messages are produced for; some compilers have multiple options
there.

It is my opinion that these restrictions were misguided in the first
place. They achieved nothing useful and disallowed otherwise reasonable
coding practices. I think that a majority of J3 eventually came to agree
with that. AT any case, they did agree with removing the restrictions in
f2003.

--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.

Relevant Pages

  • Re: generic module procedures with function arguments
    ... even when using strict standard adherance compiler switches. ... > module procedure GQC ... is there any way to correct to be standard conforming ... I tried with 3 compilers: ...
    (comp.lang.fortran)
  • Re: why doesnt this compile ?
    ... >> restricted to being a module procedure just because it is strange to ... I wasn't aware that it was existing practice to allow procedures ... existing compilers are required to be able to at least diagnose it. ... good reason is a different matter from whether it is a reason. ...
    (comp.lang.fortran)