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)
- From: Paul Thomas <paulthomas2 at wanadoo dot fr>
- To: Paul Brook <paul at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Steve Kargl <sgk at troutmask dot apl dot washington dot edu>, "'fortran at gcc dot gnu dot org'" <fortran at gcc dot gnu dot org>
- Date: Sun, 29 Jan 2006 13:42:57 +0100
- Subject: Re: [Patch, fortran] PR18578, PR18579, PR20857 and PR20885 - Constraints on INTENT(OUT and INOUT)
- References: <43DC66F8.50306@wanadoo.fr> <200601291213.35379.paul@codesourcery.com>
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.
It is such a long time since I wrote this patch that I have quite
forgotten why the normal unused parameter/variable warnings do not work
- I will remind myself.
Thanks
Paul