From patchwork Thu Jun 10 20:00:55 2010
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [fortran,doc] Document that Cray pointers cannot be function results
Date: Thu, 10 Jun 2010 10:00:55 -0000
From: FX <fxcoudert@gmail.com>
X-Patchwork-Id: 55247
Message-Id: <27E442CA-BD61-4814-B0E0-8ADF5005DD33@gmail.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Fortran List <fortran@gcc.gnu.org>, gcc-patches@gcc.gnu.org

> IMHO, as long as "make info html pdf"
> completes without error go ahead an commit
> your patches.  The gfortran manual can always
> use improvements.

OK, I guess people can then later on expand it if they find better wording.

So, here's what I committed (sorry for the wrong patch):


Index: gfortran.texi
===================================================================
--- gfortran.texi	(revision 160470)
+++ gfortran.texi	(working copy)
@@ -1515,10 +1515,10 @@ to Cray pointers and pointees.  Pointees
 @code{ALLOCATABLE}, @code{INTENT}, @code{OPTIONAL}, @code{DUMMY},
 @code{TARGET}, @code{INTRINSIC}, or @code{POINTER} attributes. Pointers
 may not have the @code{DIMENSION}, @code{POINTER}, @code{TARGET},
-@code{ALLOCATABLE}, @code{EXTERNAL}, or @code{INTRINSIC} attributes.
-Pointees may not occur in more than one pointer statement.  A pointee
-cannot be a pointer.  Pointees cannot occur in equivalence, common, or
-data statements.
+@code{ALLOCATABLE}, @code{EXTERNAL}, or @code{INTRINSIC} attributes, nor
+may they be function results. Pointees may not occur in more than one
+pointer statement.  A pointee cannot be a pointer.  Pointees cannot occur
+in equivalence, common, or data statements.
 
 A Cray pointer may also point to a function or a subroutine.  For
 example, the following excerpt is valid: