This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [wwwdata] Update Fortran section of gcc-4.6/changes.html
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Tobias Burnus <burnus at net-b dot de>, gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Wed, 15 Dec 2010 14:38:53 -0800
- Subject: Re: [wwwdata] Update Fortran section of gcc-4.6/changes.html
- References: <4C6CE567.2080200@net-b.de> <alpine.LNX.2.00.1012160622500.29221@gerinyyl.fvgr>
On Thu, Dec 16, 2010 at 06:26:31AM +0800, Gerald Pfeifer wrote:
> On Thu, 19 Aug 2010, Tobias Burnus wrote:
> > I have already committed the attached patch, but don't hesitate to suggest
> > changes or other improvements.
> >
> > Cf. http://gcc.gnu.org/gcc-4.6/changes.html#Fortran
>
> The following snippet sounds a bit confusing to me, though admittedly
> I am not a Fortran hacker:
>
> + <li>Null pointers (including <code>NULL()</code>) and not
> + allocated variables can be used as actual argument to optional
> + non-pointer, non-allocatable dummy arguments, denoting an absent
> + argument.</li>
>
> Is "actual argument" a standard term? "as actual argument to ...
> arguments, denoting an absent argument" sounds a bit tricky.
Yes, "actual argument" is a standard term.
program test
integer i
call foo(i) ! i is the actual argument.
end program test
subroutine foo(j) ! j is the dummy argument.
integer j
print *, j
end subroutine foo
In the standard, one finds passages of like "'i' is the
actual argument associated with the dummy argument 'j'".
I'll suggest a rewording of the form
<li>Null pointers and unallocated allocatable variables can be used
as actual arguments to optional non-pointer, non-allocatable
dummy arguments to denote an absent argument.</li>
--
Steve