This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
g77 (mostly) doc patch
- To: egcs-patches at egcs dot cygnus dot com
- Subject: g77 (mostly) doc patch
- From: craig at jcb-sc dot com
- Date: 17 Feb 1999 16:44:24 -0000
- Cc: craig at jcb-sc dot com
I've just committed this doc patch, which also fixes an
obscure spelling problem (that probably nobody but me cares about).
tq vm, (burley)
1999-02-17 Craig Burley <craig@jcb-sc.com>
* g77.texi, intdoc.in: Document Y2K and some other known
limitations.
* intrin.def (DTIME, FDATE): Fix capitalization of
case-sensitive forms of these intrinsics' names.
*** g77-e/gcc/f/g77.texi.~1~ Tue Feb 16 22:03:48 1999
--- g77-e/gcc/f/g77.texi Wed Feb 17 11:30:34 1999
***************
*** 15,22 ****
@setfilename g77.info
! @set last-up-date 1999-02-14
@set version-g77 0.5.24
@set email-general egcs@@egcs.cygnus.com
@set email-bugs egcs-bugs@@egcs.cygnus.com
@set path-g77 egcs/gcc/f
@set path-libf2c egcs/libf2c
--- 15,23 ----
@setfilename g77.info
! @set last-up-date 1999-02-17
@set version-g77 0.5.24
@set email-general egcs@@egcs.cygnus.com
@set email-bugs egcs-bugs@@egcs.cygnus.com
+ @set email-burley craig@@jcb-sc.com
@set path-g77 egcs/gcc/f
@set path-libf2c egcs/libf2c
*************** original English.
*** 100,104 ****
@end ifinfo
! Contributed by James Craig Burley (@email{craig@@jcb-sc.com}).
Inspired by a first pass at translating @file{g77-0.5.16/f/DOC} that
was contributed to Craig by David Ronis (@email{ronis@@onsager.chem.mcgill.ca}).
--- 101,105 ----
@end ifinfo
! Contributed by James Craig Burley (@email{@value{email-burley}}).
Inspired by a first pass at translating @file{g77-0.5.16/f/DOC} that
was contributed to Craig by David Ronis (@email{ronis@@onsager.chem.mcgill.ca}).
*************** was contributed to Craig by David Ronis
*** 118,122 ****
@page
@vskip 0pt plus 1filll
! Copyright @copyright{} 1995-1997 Free Software Foundation, Inc.
@sp 2
For GNU Fortran Version @value{version-g77}*
--- 119,123 ----
@page
@vskip 0pt plus 1filll
! Copyright @copyright{} 1995-1999 Free Software Foundation, Inc.
@sp 2
For GNU Fortran Version @value{version-g77}*
*************** without royalty; alteration is not permi
*** 776,780 ****
Work on GNU Fortran is still being done mostly by its author,
! James Craig Burley (@email{craig@@jcb-sc.com}), who is a volunteer
for, not an employee of, the Free Software Foundation (FSF).
As with other GNU software, funding is important because it can pay for
--- 777,781 ----
Work on GNU Fortran is still being done mostly by its author,
! James Craig Burley (@email{@value{email-burley}}), who is a volunteer
for, not an employee of, the Free Software Foundation (FSF).
As with other GNU software, funding is important because it can pay for
*************** Specify status of VXT intrinsics.
*** 2218,2221 ****
--- 2219,2223 ----
@cindex length of source lines
@cindex fixed form
+ @cindex limits, lengths of source lines
Set column after which characters are ignored in typical fixed-form
lines in the source file, and through which spaces are assumed (as
*************** for the relevant aspects of GNU Fortran.
*** 4658,4661 ****
--- 4660,4664 ----
(Corresponds to Section 2.2 of ANSI X3.9-1978 FORTRAN 77.)
+ @cindex limits, lengths of names
In GNU Fortran, a symbolic name is at least one character long,
and has no arbitrary upper limit on length.
*************** of work!}
*** 7970,7973 ****
--- 7973,7977 ----
@menu
* Compiler Limits::
+ * Run-time Environment Limits::
* Compiler Types::
* Compiler Constants::
*************** symbols in a program, and so on.
*** 7988,7991 ****
--- 7992,7997 ----
@cindex options, -Nx
@cindex -Nx option
+ @cindex limits, continuation lines
+ @cindex limits, lengths of names
For example, some other Fortran compiler have an option
(such as @samp{-Nl@var{x}}) to increase the limit on the
*************** limits in these areas.
*** 8003,8009 ****
@cindex number of dimensions, maximum
@cindex maximum number of dimensions
@code{g77} does currently limit the number of dimensions in an array
to the same degree as do the Fortran standards---seven (7).
! This restriction might well be lifted in a future version.
@node Compiler Types
--- 8009,8208 ----
@cindex number of dimensions, maximum
@cindex maximum number of dimensions
+ @cindex limits, rank
+ @cindex limits, array dimensions
@code{g77} does currently limit the number of dimensions in an array
to the same degree as do the Fortran standards---seven (7).
! This restriction might be lifted in a future version.
!
! @node Run-time Environment Limits
! @section Run-time Environment Limits
! @cindex limits, run-time library
! @cindex wraparound
!
! As a portable Fortran implementation,
! @code{g77} offers its users direct access to,
! and otherwise depends upon,
! the underlying facilities of the system
! used to build @code{g77},
! the system on which @code{g77} itself is used to compile programs,
! and the system on which the @code{g77}-compiled program is actually run.
! (For most users, the three systems are of the same
! type---combination of operating environment and hardware---often
! the same physical system.)
!
! The run-time environment for a particular system
! inevitably imposes some limits on a program's use
! of various system facilities.
! These limits vary from system to system.
!
! Even when such limits might be well beyond the
! possibility of being encountered on a particular system,
! the @code{g77} run-time environment
! has certain built-in limits,
! usually, but not always, stemming from intrinsics
! with inherently limited interfaces.
!
! Currently, the @code{g77} run-time environment
! does not generally offer a less-limiting environment
! by augmenting the underlying system's own environment.
!
! Therefore, code written in the GNU Fortran language,
! while syntactically and semantically portable,
! might nevertheless make non-portable assumptions
! about the run-time environment---assumptions that
! prove to be false for some particular environments.
!
! The GNU Fortran language,
! the @code{g77} compiler and run-time environment,
! and the @code{g77} documentation
! do not yet offer comprehensive portable work-arounds for such limits,
! though programmers should be able to
! find their own in specific instances.
!
! Not all of the limitations are described in this document.
! Some of the known limitations include:
!
! @menu
! * Timer Wraparounds::
! * Year 2000 (Y2K) Problems::
! * Array Size::
! * Character-variable Length::
! * Year 10000 (Y10K) Problems::
! @end menu
!
! @node Timer Wraparounds
! @subsection Timer Wraparounds
!
! Intrinsics that return values computed from system timers,
! whether elapsed (wall-clock) timers,
! process CPU timers,
! or other kinds of timers,
! are prone to experiencing wrap-around errors
! (or returning wrapped-around values from successive calls)
! due to insufficient ranges
! offered by the underlying system's timers.
!
! @cindex negative time
! @cindex short time
! @cindex long time
! Some of the symptoms of such behaviors include
! apparently negative time being computed for a duration,
! an extremely short amount of time being computed for a long duration,
! and an extremely long amount of time being computed for a short duration.
!
! See the following for intrinsics
! known to have potential problems in these areas
! on at least some systems:
! @ref{CPU_Time Intrinsic},
! @ref{DTime Intrinsic (function)}, @ref{DTime Intrinsic (subroutine)},
! @ref{ETime Intrinsic (function)}, @ref{ETime Intrinsic (subroutine)},
! @ref{MClock Intrinsic}, @ref{MClock8 Intrinsic},
! @ref{Secnds Intrinsic},
! @ref{Second Intrinsic (function)}, @ref{Second Intrinsic (subroutine)},
! @ref{System_Clock Intrinsic},
! @ref{Time Intrinsic (UNIX)}, @ref{Time Intrinsic (VXT)},
! @ref{Time8 Intrinsic}.
!
! @node Year 2000 (Y2K) Problems
! @subsection Year 2000 (Y2K) Problems
! @cindex Y2K compliance
! @cindex Year 2000 compliance
!
! While the @code{g77} compiler itself is believed to
! be Year-2000 (Y2K) compliant,
! some intrinsics are not,
! and, potentially, some underlying systems are not,
! perhaps rendering some Y2K-compliant intrinsics
! non-compliant when used on those particular systems.
!
! Fortran code that uses non-Y2K-compliant intrinsics
! (listed below)
! is, itself, almost certainly not compliant,
! and should be modified to use Y2K-compliant intrinsics instead.
!
! Fortran code that uses no non-Y2K-compliant intrinsics,
! but which currently is running on a non-Y2K-compliant system,
! can be made more Y2K compliant by compiling and
! linking it for use on a new Y2K-compliant system,
! such as a new version of an old, non-Y2K-compliant, system.
!
! Currently, information on Y2K and related issues
! is being maintained at
! @uref{http://www.gnu.org/software/year2000-list.html}.
!
! See the following for intrinsics
! known to have potential problems in these areas
! on at least some systems:
! @ref{Date Intrinsic},
! @ref{IDate Intrinsic (VXT)}.
!
! @node Array Size
! @subsection Array Size
! @cindex limits, array size
! @cindex array size
!
! Currently, @code{g77} uses the default @code{INTEGER} type
! for array indexes,
! which limits the sizes of single-dimension arrays
! on systems offering a larger address space
! than can be addressed by that type.
! (That @code{g77} puts all arrays in memory
! could be considered another limitation---it
! could use large temporary files---but that decision
! is left to the programmer as an implementation choice
! by most Fortran implementations.)
!
! @c ??? Investigate this, to offer a more clear statement
! @c than the following paragraphs do. -- burley 1999-02-17
! It is not yet clear whether this limitation
! never, sometimes, or always applies to the
! sizes of multiple-dimension arrays as a whole.
!
! For example, on a system with 64-bit addresses
! and 32-bit default @code{INTEGER},
! an array with a size greater than can be addressed
! by a 32-bit offset
! can be declared using multiple dimensions.
! Such an array is therefore larger
! than a single-dimension array can be,
! on the same system.
!
! @cindex limits, multi-dimension arrays
! @cindex multi-dimension arrays
! @cindex arrays, dimensioning
! Whether large multiple-dimension arrays are reliably supported
! depends mostly on the @code{gcc} back end (code generator)
! used by @code{g77}, and has not yet been fully investigated.
!
! @node Character-variable Length
! @subsection Character-variable Length
! @cindex limits, on character-variable length
! @cindex character-variable length
!
! Currently, @code{g77} uses the default @code{INTEGER} type
! for the lengths of @code{CHARACTER} variables
! and array elements.
!
! This means that, for example,
! a system with a 64-bit address space
! and a 32-bit default @code{INTEGER} type
! does not, under @code{g77},
! support a @code{CHARACTER*@var{n}} declaration
! where @var{n} is greater than 2147483647.
!
! @node Year 10000 (Y10K) Problems
! @subsection Year 10000 (Y10K) Problems
! @cindex Y10K compliance
! @cindex Year 10000 compliance
!
! Most intrinsics returning, or computing values based on,
! date information are prone to Year-10000 (Y10K) problems,
! due to supporting only 4 digits for the year.
!
! See the following for examples:
! @ref{FDate Intrinsic (function)}, @ref{FDate Intrinsic (subroutine)},
! @ref{IDate Intrinsic (UNIX)},
! @ref{Time Intrinsic (VXT)},
! @ref{Date_and_Time Intrinsic}.
@node Compiler Types
*************** bugs that lead to these behaviors is, ul
*** 11488,11492 ****
responsibility, as difficult as that task can sometimes be.
! @cindex ``infinite spaces'' printed
@cindex space, endless printing of
@cindex libc, non-ANSI or non-default
--- 11687,11691 ----
responsibility, as difficult as that task can sometimes be.
! @cindex infinite spaces printed
@cindex space, endless printing of
@cindex libc, non-ANSI or non-default
*** g77-e/gcc/f/intdoc.in.~1~ Tue Feb 16 21:46:52 1999
--- g77-e/gcc/f/intdoc.in Wed Feb 17 11:04:33 1999
*************** abbreviation of the month name @var{mmm}
*** 1060,1064 ****
--- 1060,1068 ----
the year @var{yy}, e.g.@: @samp{25-Nov-96}.
+ @cindex Y2K compliance
+ @cindex Year 2000 compliance
This intrinsic is not recommended, due to the year 2000 approaching.
+ Therefore, programs making use of this intrinsic
+ might not be Year 2000 (Y2K) compliant.
@xref{CTime Intrinsic (subroutine)}, for information on obtaining more digits
for the current (or any) date.
*************** Subsequent invocations of @samp{@0@()} r
*** 1076,1079 ****
--- 1080,1093 ----
previous invocation.
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
+
Due to the side effects performed by this intrinsic, the function
form is not recommended.
*************** Subsequent invocations of @samp{@0@()} s
*** 1091,1094 ****
--- 1105,1118 ----
since the previous invocation.
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
+
Some non-GNU implementations of Fortran provide this intrinsic as
only a function, not as a subroutine.
*************** and the user and system components of th
*** 1102,1105 ****
--- 1126,1139 ----
and @samp{@var{@1@}(2)} respectively.
The functions' value is equal to @samp{@var{@1@}(1) + @var{@1@}(2)}.
+
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
")
*************** and @samp{@var{@2@}(2)} respectively.
*** 1112,1115 ****
--- 1146,1159 ----
The value of @var{@1@} is equal to @samp{@var{@2@}(1) + @var{@2@}(2)}.
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
+
Some non-GNU implementations of Fortran provide this intrinsic as
only a function, not as a subroutine.
*************** CTIME(TIME8())
*** 1125,1128 ****
--- 1169,1183 ----
@end example
+ @cindex Y10K compliance
+ @cindex Year 10000 compliance
+ @cindex wraparound, Y10K
+ @cindex limits, Y10K
+ Programs making use of this intrinsic
+ might not be Year 10000 (Y10K) compliant.
+ For example, the date might appear,
+ to such programs, to wrap around
+ (change from a larger value to a smaller one)
+ as of the Year 10000.
+
@xref{CTime Intrinsic (function)}.
")
*************** CALL CTIME(@var{@1@}, TIME8())
*** 1138,1141 ****
--- 1193,1207 ----
@end example
+ @cindex Y10K compliance
+ @cindex Year 10000 compliance
+ @cindex wraparound, Y10K
+ @cindex limits, Y10K
+ Programs making use of this intrinsic
+ might not be Year 10000 (Y10K) compliant.
+ For example, the date might appear,
+ to such programs, to wrap around
+ (change from a larger value to a smaller one)
+ as of the Year 10000.
+
@xref{CTime Intrinsic (subroutine)}.
*************** of day, month (in the range 1--12), and
*** 1227,1230 ****
--- 1293,1307 ----
respectively.
The year has four significant digits.
+
+ @cindex Y10K compliance
+ @cindex Year 10000 compliance
+ @cindex wraparound, Y10K
+ @cindex limits, Y10K
+ Programs making use of this intrinsic
+ might not be Year 10000 (Y10K) compliant.
+ For example, the date might appear,
+ to such programs, to wrap around
+ (change from a larger value to a smaller one)
+ as of the Year 10000.
")
*************** the day (in the range 1--7) in @var{@2@}
*** 1235,1239 ****
--- 1312,1329 ----
and the year in @var{@3@} (in the range 0--99).
+ @cindex Y2K compliance
+ @cindex Year 2000 compliance
+ @cindex wraparound, Y2K
+ @cindex limits, Y2K
This intrinsic is not recommended, due to the year 2000 approaching.
+ Therefore, programs making use of this intrinsic
+ might not be Year 2000 (Y2K) compliant.
+ For example, the date might appear,
+ to such programs, to wrap around
+ (change from a larger value to a smaller one)
+ as of the Year 2000.
+
+ @xref{IDate Intrinsic (UNIX)}, for information on obtaining more digits
+ for the current date.
")
*************** Returns the number of clock ticks since
*** 1247,1253 ****
--- 1337,1350 ----
Supported on systems with @code{clock(3)} (q.v.).
+ @cindex wraparound, timings
+ @cindex limits, timings
This intrinsic is not fully portable, such as to systems
with 32-bit @code{INTEGER} types but supporting times
wider than 32 bits.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
+
@xref{MClock8 Intrinsic}, for information on a
similar intrinsic that might be portable to more
*************** Returns the number of clock ticks since
*** 1263,1266 ****
--- 1360,1365 ----
Supported on systems with @code{clock(3)} (q.v.).
+ @cindex wraparound, timings
+ @cindex limits, timings
@emph{Warning:} this intrinsic does not increase the range
of the timing values over that returned by @code{clock(3)}.
*************** On a system with a 32-bit @code{clock(3)
*** 1269,1272 ****
--- 1368,1375 ----
even though converted to an @samp{INTEGER(KIND=2)} value.
That means overflows of the 32-bit value can still occur.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
No Fortran implementations other than GNU Fortran are
*************** DEFDOC (SECNDS, "Get local time offset s
*** 1284,1287 ****
--- 1387,1398 ----
Returns the local time in seconds since midnight minus the value
@var{@1@}.
+
+ @cindex wraparound, timings
+ @cindex limits, timings
+ This values returned by this intrinsic
+ become numerically less than previous values
+ (they wrap around) during a single run of the
+ compiler program, under normal circumstances
+ (such as running through the midnight hour).
")
*************** DEFDOC (SECOND_func, "Get CPU time for p
*** 1289,1292 ****
--- 1400,1413 ----
Returns the process's runtime in seconds---the same value as the
UNIX function @code{etime} returns.
+
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
")
*************** Returns the process's runtime in seconds
*** 1295,1298 ****
--- 1416,1429 ----
as the UNIX function @code{etime} returns.
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
+
This routine is known from Cray Fortran. @xref{CPU_Time Intrinsic},
for a standard equivalent.
*************** isn't in general.
*** 1308,1311 ****
--- 1439,1452 ----
in this implementation since it's just the maximum C @code{unsigned
int} value.
+
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
")
*************** Returns in @var{@1@} the current value o
*** 1314,1317 ****
--- 1455,1468 ----
This implementation of the Fortran 95 intrinsic is just an alias for
@code{second} @xref{Second Intrinsic (subroutine)}.
+
+ @cindex wraparound, timings
+ @cindex limits, timings
+ On some systems, the underlying timings are represented
+ using types with sufficiently small limits that overflows
+ (wraparounds) are possible, such as 32-bit types.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
")
*************** This value is suitable for passing to @c
*** 1322,1325 ****
--- 1473,1478 ----
@code{GMTIME}, and @code{LTIME}.
+ @cindex wraparound, timings
+ @cindex limits, timings
@emph{Warning:} this intrinsic does not increase the range
of the timing values over that returned by @code{time(3)}.
*************** On a system with a 32-bit @code{time(3)}
*** 1328,1331 ****
--- 1481,1488 ----
even though converted to an @samp{INTEGER(KIND=2)} value.
That means overflows of the 32-bit value can still occur.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
No Fortran implementations other than GNU Fortran are
*************** This value is suitable for passing to @c
*** 1343,1349 ****
--- 1500,1513 ----
@code{GMTIME}, and @code{LTIME}.
+ @cindex wraparound, timings
+ @cindex limits, timings
This intrinsic is not fully portable, such as to systems
with 32-bit @code{INTEGER} types but supporting times
wider than 32 bits.
+ Therefore, the values returned by this intrinsic
+ might be, or become, negative,
+ or numerically less than previous values,
+ during a single run of the compiled program.
+
@xref{Time8 Intrinsic}, for information on a
similar intrinsic that might be portable to more
*************** Returns in @var{@1@} a character represe
*** 2410,2413 ****
--- 2574,2588 ----
obtained from @code{ctime(3)}.
+ @cindex Y10K compliance
+ @cindex Year 10000 compliance
+ @cindex wraparound, Y10K
+ @cindex limits, Y10K
+ Programs making use of this intrinsic
+ might not be Year 10000 (Y10K) compliant.
+ For example, the date might appear,
+ to such programs, to wrap around
+ (change from a larger value to a smaller one)
+ as of the Year 10000.
+
@xref{Fdate Intrinsic (subroutine)} for an equivalent routine.
")
*************** minutes from UTC, hour of the day, minut
*** 2506,2509 ****
--- 2681,2695 ----
of the second in successive values of the array.
@end table
+
+ @cindex Y10K compliance
+ @cindex Year 10000 compliance
+ @cindex wraparound, Y10K
+ @cindex limits, Y10K
+ Programs making use of this intrinsic
+ might not be Year 10000 (Y10K) compliant.
+ For example, the date might appear,
+ to such programs, to wrap around
+ (change from a larger value to a smaller one)
+ as of the Year 10000.
On systems where a millisecond timer isn't available, the millisecond
*** g77-e/gcc/f/intrin.def.~1~ Wed Dec 16 16:17:31 1998
--- g77-e/gcc/f/intrin.def Wed Feb 17 10:56:03 1999
*************** DEFNAME ("DTAN", "dtan", "DTan", genNO
*** 134,138 ****
DEFNAME ("DTAND", "dtand", "DTanD", genNONE, specDTAND) /* VXT */
DEFNAME ("DTANH", "dtanh", "DTanH", genNONE, specDTANH)
! DEFNAME ("DTIME", "dtime", "Dtime", genDTIME, specNONE) /* UNIX */
DEFNAME ("EOSHIFT", "eoshift", "EOShift", genNONE, specEOSHIFT) /* F90 */
DEFNAME ("EPSILON", "epsilon", "Epsilon", genNONE, specEPSILON) /* F90 */
--- 134,138 ----
DEFNAME ("DTAND", "dtand", "DTanD", genNONE, specDTAND) /* VXT */
DEFNAME ("DTANH", "dtanh", "DTanH", genNONE, specDTANH)
! DEFNAME ("DTIME", "dtime", "DTime", genDTIME, specNONE) /* UNIX */
DEFNAME ("EOSHIFT", "eoshift", "EOShift", genNONE, specEOSHIFT) /* F90 */
DEFNAME ("EPSILON", "epsilon", "Epsilon", genNONE, specEPSILON) /* F90 */
*************** DEFNAME ("EXIT", "exit", "Exit", genNO
*** 143,147 ****
DEFNAME ("EXP", "exp", "Exp", genNONE, specEXP)
DEFNAME ("EXPONENT", "exponent", "Exponent", genNONE, specEXPONENT) /* F90 */
! DEFNAME ("FDATE", "fdate", "Fdate", genFDATE, specNONE) /* UNIX */
DEFNAME ("FGET", "fget", "FGet", genFGET, specNONE) /* UNIX */
DEFNAME ("FGETC", "fgetc", "FGetC", genFGETC, specNONE) /* UNIX */
--- 143,147 ----
DEFNAME ("EXP", "exp", "Exp", genNONE, specEXP)
DEFNAME ("EXPONENT", "exponent", "Exponent", genNONE, specEXPONENT) /* F90 */
! DEFNAME ("FDATE", "fdate", "FDate", genFDATE, specNONE) /* UNIX */
DEFNAME ("FGET", "fget", "FGet", genFGET, specNONE) /* UNIX */
DEFNAME ("FGETC", "fgetc", "FGetC", genFGETC, specNONE) /* UNIX */