diff options
| author | Mark Eggleston <mark.eggleston@codethink.com> | 2019-05-20 15:49:33 -0600 |
|---|---|---|
| committer | Jeff Law <law@gcc.gnu.org> | 2019-05-20 15:49:33 -0600 |
| commit | 593ac6c6b3a704804bb5b55b12c49d53b5370007 (patch) | |
| tree | ff9c2b2e5700c3a081a34c0e33b363d5844975f3 /gcc | |
| parent | 500e4868bf5c89a3136fb329293872d29632ffad (diff) | |
| download | gcc-593ac6c6b3a704804bb5b55b12c49d53b5370007.zip gcc-593ac6c6b3a704804bb5b55b12c49d53b5370007.tar.gz gcc-593ac6c6b3a704804bb5b55b12c49d53b5370007.tar.bz2 | |
gfortran.texi: Remove reference to the ASSIGN statement...
* gfortran.texi: Remove reference to the ASSIGN statement, capitalise
complex, state that padding is with spaces and modify the Hollerith
constant examples.
From-SVN: r271441
Diffstat (limited to 'gcc')
| -rw-r--r-- | gcc/fortran/ChangeLog | 6 | ||||
| -rw-r--r-- | gcc/fortran/gfortran.texi | 20 |
2 files changed, 17 insertions, 9 deletions
diff --git a/gcc/fortran/ChangeLog b/gcc/fortran/ChangeLog index dd54e59..e5215aa 100644 --- a/gcc/fortran/ChangeLog +++ b/gcc/fortran/ChangeLog @@ -1,3 +1,9 @@ +2019-05-20 Mark Eggleston <markeggleston@codethink.com> + + * gfortran.texi: Remove reference to the ASSIGN statement, capitalise + complex, state that padding is with spaces and modify the Hollerith + constant examples. + 2019-05-19 Paul Thomas <pault@gcc.gnu.org> PR fortran/90498 diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi index 76c1f2d..6c746e3 100644 --- a/gcc/fortran/gfortran.texi +++ b/gcc/fortran/gfortran.texi @@ -1901,13 +1901,13 @@ in I/O operations. @cindex Hollerith constants 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 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 -constant will be padded or truncated to fit the size of the variable in -which it is stored. +arguments, and @code{DATA} statements. A Hollerith 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 constant will be padded +with spaces or truncated to fit the size of the variable in which it is +stored. Examples of valid uses of Hollerith constants: @smallexample @@ -1917,11 +1917,13 @@ Examples of valid uses of Hollerith constants: call foo (4h abc) @end smallexample -Invalid Hollerith constants examples: +Examples of Hollerith constants: @smallexample integer*4 a + a = 0H ! Invalid, at least one character is needed. + a = 4HAB12 ! Valid a = 8H12345678 ! Valid, but the Hollerith constant will be truncated. - a = 0H ! At least one character is needed. + a = 3Hxyz ! Valid, but the Hollerith constant will be padded. @end smallexample In general, Hollerith constants were used to provide a rudimentary |