> I understand that an array becomes undefined the moment it is passed to
> a subroutine, if the respective dummy argument is INTENT(OUT). So if the
> subroutine doesn't assign values to the whole array, the rest of the
> array remains undefined. And then, as I read in a posting by Richard
> Maine, the whole array is undefined because

>  > In 14.7.1 we find "An object is defined if and only if all of its
>  > subobjects are defined."

> But what about the following example, where only an array section is
> passed to a subroutine:

> MODULE mo_fill
>    !
> CONTAINS
>    !
> SUBROUTINE se_fill(k)
>    IMPLICIT NONE
>    INTEGER,INTENT(OUT) :: k(:,:)
>    k = 3
> END SUBROUTINE se_fill
>    !
> END MODULE mo_fill
>    !
> PROGRAM pr_section
>    USE mo_fill ,ONLY : se_fill
>    IMPLICIT NONE
>    INTEGER :: ji
>    INTEGER :: jj
>    INTEGER :: k(1:2,1:2)
>    !
>    k = 0
>    CALL se_fill(k(1:1,1:1))
>    DO ji = 1,2
>       DO jj = 1,2
>          PRINT *,jj,ji,k(jj,ji)
>       ENDDO
>    ENDDO
> END PROGRAM pr_section

> I would assume that on entry to se_fill, INTENT(OUT) deletes the
> definition of the array elements which are actually passed. Since the
> information is fully restored within the subroutine, the temporary loss
> of definition shouldn't do any harm outside se_fill.

> When compiled with the Fujitsu Fortran Compiler Driver Version 5.1.1 and
> option -Eg, the program output reads:

>   1 1 3
> jwe0323i-w line 24 The variable (k(2,1)) has an undefined value.
>   error occurs at MAIN__   line 24 loc 00010c58 offset 000002c4
>   MAIN__       at loc 00010994 called from o.s.
> taken to (standard) corrective action, execution continuing.
>   2 1 -1953789045
>   1 2 0
>   2 2 0

> Is this a bug in the program or a bug of the compiler?
> Does the f95 standard really want me to either in se_fill declare k
> INTENT(INOUT) or do an explicit copy of the array section in the calling
> procedure, like

>    INTEGER :: k(1:2,1:2)
>    INTEGER :: ksection(1:1,1:1)
>    !
>    k = 0
>    CALL se_fill(ksection(1:1,1:1))
>    k(1:1,1:1) = ksection

> ---
> Alfred Trukenmller
> MI, Universit?t Hamburg
> Hamburg, Germany

> To use automatic array in subroutine or function, it must be declared with
> INTENT(INOUT) when the array is modified in the sub-program : the compiler
> must find the correct dimension of this array at the call.

> Hi Alfred

> To use automatic array in subroutine or function, it must be declared with
> INTENT(INOUT) when the array is modified in the sub-program : the compiler
> must find the correct dimension of this array at the call.

> The array used in the example is an assumed-size array.

> Is this a bug in the program or a bug of the compiler?

>   This looks like a bug in an older version of the compiler. I tried
> your code with LF95 v5.7 using the -chk, -chkglobal and -Eg options,
> and always got these results:

> 1 1 3
> 2 1 0
> 1 2 0
> 2 2 0