Patchwork [fortran,doc] Document that Cray pointers cannot be function results

login
register
mail settings
Submitter FX
Date June 10, 2010, 8 p.m.
Message ID <27E442CA-BD61-4814-B0E0-8ADF5005DD33@gmail.com>
Download mbox | patch
Permalink /patch/55247/
State New
Headers show

Comments

FX - June 10, 2010, 8 p.m.
> 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):

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: