doc improvements

From-SVN: r26806
This commit is contained in:
Craig Burley 1999-05-06 09:46:21 +00:00 committed by Craig Burley
parent 52dff54a7f
commit 6a84329681
2 changed files with 26 additions and 14 deletions

View File

@ -1,3 +1,9 @@
Thu May 6 12:40:21 1999 Craig Burley <craig@jcb-sc.com>
* g77.texi (Arbitrary Concatenation): Put this under
"Missing Features" instead of "Projects".
(Internals Documentation): Point to new "Front End" chapter.
Thu May 6 08:23:52 1999 Craig Burley <craig@jcb-sc.com>
* bugs.texi, news.texi: Automatic arrays reportedly working

View File

@ -11389,6 +11389,7 @@ GNU Fortran language:
* Better Source Model::
* Fortran 90 Support::
* Intrinsics in PARAMETER Statements::
* Arbitrary Concatenation::
* SELECT CASE on CHARACTER Type::
* RECURSIVE Keyword::
* Popular Non-standard Types::
@ -11529,6 +11530,22 @@ But, if the @code{gcc} back end is enhanced to provide
such a facility, @code{g77} will likely use that facility
in implementing this feature soon afterwards.
@node Arbitrary Concatenation
@subsection Arbitrary Concatenation
@cindex concatenation
@cindex CHARACTER*(*)
@cindex run-time, dynamic allocation
@code{g77} doesn't support arbitrary operands for concatenation
in contexts where run-time allocation is required.
For example:
@smallexample
SUBROUTINE X(A)
CHARACTER*(*) A
CALL FOO(A // 'suffix')
@end smallexample
@node SELECT CASE on CHARACTER Type
@subsection @code{SELECT CASE} on @code{CHARACTER} Type
@ -14057,20 +14074,6 @@ Many mentions of incomplete or missing features are
sprinkled throughout.
It is not worth repeating them here.
@item
@cindex concatenation
@cindex CHARACTER*(*)
@cindex run-time, dynamic allocation
Support arbitrary operands for concatenation, even in contexts where
run-time allocation is required.
For example:
@smallexample
SUBROUTINE X(A)
CHARACTER*(*) A
CALL FOO(A // 'suffix')
@end smallexample
@item
Consider adding a @code{NUMERIC} type to designate typeless numeric constants,
named and unnamed.
@ -14176,6 +14179,9 @@ Better info on how @code{g77} works and how to port it is needed.
Much of this should be done only after the redesign planned for
0.6 is complete.
@xref{Front End}, which contains some information
on @code{g77} internals.
@node Internals Improvements
@section Internals Improvements