[patch,gfortran] PR 22273: LEN() of INTENT(OUT) dummy

[Erik Edelmann]

On Fri, Oct 14, 2005 at 06:07:18PM -0700, Brooks Moses wrote:
> Erik Edelmann wrote:
> >+  /* At this point we have a inquiry function with a variable argument.  
> 
> That should be "an inquiry function", I suppose.  :)

Yes.


        Erik
-------------- next part --------------
Index: gcc/fortran/expr.c
===================================================================
RCS file: /cvsroot/gcc/gcc/gcc/fortran/expr.c,v
retrieving revision 1.29
diff -u -p -r1.29 expr.c
--- gcc/fortran/expr.c	17 Sep 2005 18:57:59 -0000	1.29
+++ gcc/fortran/expr.c	14 Oct 2005 10:21:43 -0000
@@ -1355,7 +1355,7 @@ check_inquiry (gfc_expr * e)
   /* FIXME: This should be moved into the intrinsic definitions,
      to eliminate this ugly hack.  */
   static const char * const inquiry_function[] = {
-    "digits", "epsilon", "huge", "kind", "maxexponent", "minexponent",
+    "digits", "epsilon", "huge", "kind", "len", "maxexponent", "minexponent",
     "precision", "radix", "range", "tiny", "bit_size", "size", "shape",
     "lbound", "ubound", NULL
   };
@@ -1376,10 +1376,9 @@ check_inquiry (gfc_expr * e)
   if (e == NULL || e->expr_type != EXPR_VARIABLE)
     return FAILURE;
 
-  /* At this point we have a numeric inquiry function with a variable
-     argument.  The type of the variable might be undefined, but we
-     need it now, because the arguments of these functions are allowed
-     to be undefined.  */
+  /* At this point we have an inquiry function with a variable argument.  The
+     type of the variable might be undefined, but we need it now, because the
+     arguments of these functions are allowed to be undefined.  */
 
   if (e->ts.type == BT_UNKNOWN)
     {