These extensions are not the sort of things users ask for "by name",
but they might improve the usability of
g77, and Fortran in
general, in the long run.
Some of these items really pertain to improving
so that some popular extensions can be more easily supported.
NUMERICtype to designate typeless numeric constants, named and unnamed. The idea is to provide a forward-looking, effective replacement for things like the old-style
PARAMETERstatement when people really need typelessness in a maintainable, portable, clearly documented way. Maybe
POINTER, and whatever else might come along. (This is not really a call for polymorphism per se, just an ability to express limited, syntactic polymorphism.)
MXUNIT-1. (This is a
OPEN(NOSPANBLOCKS,...)is treated as
OPEN(UNIT=NOSPANBLOCKS,...), so a later
UNIT=in the first example is invalid. Make sure this is what users of this feature would expect.
READ(1'10)since it is an obnoxious syntax, but supporting it might be pretty easy if needed. More details are needed, such as whether general expressions separated by an apostrophe are supported, or maybe the record number can be a general expression, and so on.
RECORDfully. Currently there is no support at all for
STRUCTUREand related syntax, whereas the rest of the stuff has at least some parsing support. This requires either major changes to
libg2cor its replacement.
g77probably disagree about label scoping relative to
END INTERFACE, and their contained procedure interface bodies (blocks?).
ENTRYdoesn't support F90
RESULT()yet, since that was added after S8.112.
OPENed,is positioned at the beginning, the end, or wherever--it might be nice to offer an option of opening to "undefined" status, requiring an explicit absolute-positioning operation to be performed before any other (besides
CLOSE) to assist in making applications port to systems (some IBM?) that
OPENto the end of a file or some such thing.