Re: Proposal for warning in gfortran documentation and man page.

[Toon Moene <toon at moene dot indiv dot nluug dot nl>]

Brooks Moses wrote:

> Steve Kargl wrote, as suggested language for this warning:

The attached is what I committed, after weighing the various comments.

Passed make info, make man and make dvi.

--
Toon Moene - e-mail: toon@moene.indiv.nluug.nl - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
A maintainer of GNU Fortran 95: http://gcc.gnu.org/fortran/
News on GNU Fortran 95: http://gfortran.org/

2005-04-12  Toon Moene  <toon@moene.indiv.nluug.nl>

	* gfortran.texi: Warn about the limited abilities
	of gfortran at this release.
	* invoke.texi: Ditto.

*** gfortran.texi.orig	Sat Apr  2 13:53:19 2005
--- gfortran.texi	Tue Apr 12 23:33:36 2005
*************** designed initially as a free replacement
*** 174,182 ****
  or alternative to, the unix @command{f95} command;
  @command{gfortran} is command you'll use to invoke the compiler.
  
! Gfortran is still in an early state of development.
! @command{gfortran} can generate code for most constructs and expressions,
! but much work remains to be done.
  
  When @command{gfortran} is finished,
  it will do everything you expect from any decent compiler: 
--- 174,191 ----
  or alternative to, the unix @command{f95} command;
  @command{gfortran} is command you'll use to invoke the compiler.
  
! @emph{Gfortran is not yet a fully conformant Fortran 95 compiler}.
! It can generate code for most constructs and expressions,
! but work remains to be done.  In particular, there are known
! deficiencies with ENTRY, NAMELIST, and sophisticated use of
! MODULES, POINTERS and DERIVED TYPES.  For those whose Fortran
! codes conform to either the Fortran 77 standard or the
! GNU Fortran 77 language, we recommend to use @command{g77}
! from GCC 3.4.  We recommend that distributors continue to provide
! packages of g77-3.4 until we announce that @command{gfortran}
! fully replaces @command{g77}.
! The gfortran developers welcome any feedback on user experience
! with @command{gfortran} at @email{fortran@@gcc.gnu.org}.
  
  When @command{gfortran} is finished,
  it will do everything you expect from any decent compiler: 
*** invoke.texi.orig	Sun Apr 10 13:14:52 2005
--- invoke.texi	Tue Apr 12 23:29:05 2005
***************
*** 1,4 ****
! @c Copyright (C) 2004
  @c Free Software Foundation, Inc.
  @c This is part of the GFORTRAN manual.   
  @c For copying conditions, see the file gfortran.texi.
--- 1,4 ----
! @c Copyright (C) 2004,2005
  @c Free Software Foundation, Inc.
  @c This is part of the GFORTRAN manual.   
  @c For copying conditions, see the file gfortran.texi.
*************** GFORTRAN@.
*** 69,74 ****
--- 69,87 ----
  The @command{gfortran} command supports all the options supported by the
  @command{gcc} command.  Only options specific to gfortran are documented here.
  
+ @emph{Gfortran is not yet a fully conformant Fortran 95 compiler}.
+ It can generate code for most constructs and expressions,
+ but work remains to be done.  In particular, there are known
+ deficiencies with ENTRY, NAMELIST, and sophisticated use of
+ MODULES, POINTERS and DERIVED TYPES.  For those whose Fortran
+ codes conform to either the Fortran 77 standard or the
+ GNU Fortran 77 language, we recommend to use @command{g77}
+ from GCC 3.4.  We recommend that distributors continue to provide
+ packages of g77-3.4 until we announce that @command{gfortran}
+ fully replaces @command{g77}.
+ The gfortran developers welcome any feedback on user experience
+ with @command{gfortran} at @email{fortran@@gcc.gnu.org}.
+ 
  @xref{Invoking GCC,,GCC Command Options,gcc,Using the GNU Compiler
  Collection (GCC)}, for information
  on the non-Fortran-specific aspects of the @command{gcc} command (and,