This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [Patch, fortran] PR18578, PR18579, PR20857 and PR20885 - Constraints on INTENT(OUT and INOUT)
Paul Brook wrote:
On Sunday 29 January 2006 12:42, Paul Thomas wrote:
Hello Paul,
Variables that aren't defined should be caught be the normal unused
parameter/variable warnings. AFAIK there's nothing special about
INTENT(OUT) that requires it be defined.
5.1.2.3 "The INTENT (OUT) attribute specifies that the dummy argument
shall be defined before a reference to the dummy argument is made within
the procedure an any actual argument that becomes associated with such a
dummy argument shall be definable. On invocation of the procedure, such
a dummy argument becomes undefiend except for the components of derived
type for which default initialization has been specified." is why I did
this. If I have misinterpreted this paragraph, I'd be quite happy to
change the error to a warning.
The error (actual argument must be definable) is ok.
Yes, indeed - the standard is more than explicit about this.
It's the warning (dummy argument not initialized) that seems redundant.
The standard only says the actual argument may be defined, not that it is
defined.
Lahey seems to agree with you on this. I interpreted "The INTENT (OUT)
attribute specifies that the dummy argument
shall be defined before a reference..." as mandating that this should be so. I guess that I have moved into the realms of note 12.17, where these checks are suggested.
Paul
- References:
- [Patch, fortran] PR18578, PR18579, PR20857 and PR20885 - Constraints on INTENT(OUT and INOUT)
- Re: [Patch, fortran] PR18578, PR18579, PR20857 and PR20885 - Constraints on INTENT(OUT and INOUT)
- Re: [Patch, fortran] PR18578, PR18579, PR20857 and PR20885 - Constraints on INTENT(OUT and INOUT)
- Re: [Patch, fortran] PR18578, PR18579, PR20857 and PR20885 - Constraints on INTENT(OUT and INOUT)