procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

gfortran.texi: Fix typos.

Browse source 
From-SVN: r120567
This commit is contained in:
Kazu Hirata 2007-01-08 01:23:16 +00:00 • committed by Kazu Hirata
parent 7a085dce62
commit 0979f01dee
2 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gcc/fortran/ChangeLog
View file

@ -1,3 +1,7 @@
2007-01-08 Kazu Hirata <kazu@codesourcery.com>
gfortran.texi: Fix typos.
2007-01-07 Steven G. Kargl <kargl@gcc.gnu.org>
* decl.c, dump-parse-tree.c, error.c, data.c, expr.c, dependency.c,

4
gcc/fortran/gfortran.texi
View file

@ -867,7 +867,7 @@ variable immediately preceding the initialization. In other words,
something like @code{INTEGER I,J/2,3/} is not valid. This style of
initialization is only allowed in declarations without double colons
(@code{::}); the double colons were introduced in Fortran 90, which also
introduced a standard syntax for initializating variables in type
introduced a standard syntax for initializing variables in type
declarations.
Examples of standard-conforming code equivalent to the above example
@ -1076,7 +1076,7 @@ zero, and @code{.TRUE.} is interpreted as one. When converting from
GNU Fortran supports Hollerith constants in assignments, function
arguments, and @code{DATA} and @code{ASSIGN} statements. A Hollerith
constant is written as a string of characters preceeded by an integer
constant is written as a string of characters preceded by an integer
constant indicating the character count, and the letter @code{H} or
@code{h}, and stored in bytewise fashion in a numeric (@code{INTEGER},
@code{REAL}, or @code{complex}) or @code{LOGICAL} variable. The