This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gfortran] Fix RETURN matcher was: Re: bug fc110
On Apr 15, 2005, at 1:36 PM, Tobias Schlüter wrote:
which rule does enforce that there
be a blank between REAL and FUNCTION and the function's name, for
instance?
There is pretty much only one place to look at for ever requiring
blanks anywhere. Remember that this is an issue specific to free source
form. Blanks make no difference in fixed source form (except in
character contexts). So it is in the section on free source form (3.3.1
of f95). The 2nd para of that section is about places where blanks are
disallowed; the 3rd para is about places where blanks are required.
Namely...
"A blank shall be used to separate names, constants, or labels from
adjacent keywords, names, constants, or labels."
The function name is a name. REAL and FUNCTION are keywords.
(Oh, and the next para is about adjacent keywords, which have a bunch
of special cases. It covers why you need the space between REAL and
FUNCTION.)
--
Richard Maine | Good judgment comes from experience;
Richard.Maine@nasa.gov | experience comes from bad judgment.
| -- Mark Twain