egcs/gcc/f/g77.texi

[craig@jcb-sc.com]

Committed.

        tq vm, (burley)


Thu Mar 11 17:32:55 1999  Craig Burley  <craig@jcb-sc.com>

	* g77.texi: Add AUTOMATIC to list of unsupported extensions.
  
*** g77-e/gcc/f/g77.texi.~1~	Sat Mar  6 02:38:52 1999
--- g77-e/gcc/f/g77.texi	Thu Mar 11 11:13:00 1999
***************
*** 15,19 ****
  @setfilename g77.info
  
! @set last-up-date 1999-03-06
  @set version-g77 0.5.24
  @set email-general egcs@@egcs.cygnus.com
--- 15,19 ----
  @setfilename g77.info
  
! @set last-up-date 1999-03-11
  @set version-g77 0.5.24
  @set email-general egcs@@egcs.cygnus.com
*************** GNU Fortran language:
*** 12000,12003 ****
--- 12000,12004 ----
  * SELECT CASE on CHARACTER Type::
  * RECURSIVE Keyword::
+ * AUTOMATIC Statement::
  * Popular Non-standard Types::
  * Full Support for Compiler Types::
*************** designed to do recursion.
*** 12157,12160 ****
--- 12158,12185 ----
  All recursive code can be rewritten to not use recursion,
  but the result is not pretty.
+ 
+ @node AUTOMATIC Statement
+ @subsection @code{AUTOMATIC} Statement
+ @cindex @code{AUTOMATIC} statement
+ @cindex statements, @code{AUTOMATIC}
+ @cindex automatic variables
+ @cindex variables, automatic
+ 
+ @code{g77} doesn't support the @code{AUTOMATIC} keyword that
+ @code{f2c} does.
+ 
+ It is not yet clear exactly what this statement would achieve.
+ The semantic equivalent would be provided by @code{RECURSIVE}
+ combined with lack of @code{SAVE}.
+ In that sense, perhaps all it would provide is an
+ overriding of an unadorned (blanket) @code{SAVE} statement
+ for specific variables.
+ 
+ It might also serve as a hint to the compiler that placing
+ even a very large array on the stack is acceptable.
+ 
+ Perhaps it should disallow @code{DATA}
+ or other specification of any initial values
+ for affected variables as well.
  
  @node Increasing Precision/Range