This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/58000] Accept OPEN( ... NAME=) with -std=legacy


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58000

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu.org

--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #3)
> Patch I am planning to submit
> 
> --- ../_clean/gcc/fortran/gfortran.texi	2016-01-04 19:51:09.000000000 +0100
> +++ gcc/fortran/gfortran.texi	2016-04-10 14:00:11.000000000 +0200
> @@ -2148,6 +2148,7 @@ code that uses them running with the GNU
>  @c * Omitted arguments in procedure call::
>  * Alternate complex function syntax::
>  * Volatile COMMON blocks::
> +* OPEN( ... NAME=)::
>  @end menu
>  
>  
> @@ -2355,6 +2356,19 @@ invalid standard Fortran syntax and is n
>  
>  
>  
> +@node OPEN( ... NAME=)
> +@subsection @code{OPEN( ... NAME=)}
> +@cindex @code{NAM}
> +
> +Some Fortran compilers, including @command{g77}, let the user declare
> +@code{OPEN( ... NAME=)}. This is
> +invalid standard Fortran syntax and is not supported by
> +@command{gfortran}.  @code{OPEN( ... NAME=)} should be replaced
> +with @code{OPEN( ... FILE=)}.
> +
> +
> +
> +@c ---------------------------------------------------------------------
>  @c ---------------------------------------------------------------------
>  @c Mixed-Language Programming
>  @c ---------------------------------------------------------------------

Approved! Please proceed.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]