uniqueness of {if,do,case}-construct-name

I've read through Chapter 8 of Final Committe Draft of the
Fortran 95 standard, and I can't find where the if-construct-name,
do-construct-name, and case-construct-name are required to be
unique. Is such a constraint mandated by the standard? Consider

program f
integer i
loop: do i = 1, 5
print *, i
end do loop
loop: do i = 1, 5
print *, i
end do loop
end program f

NAG's compiler and Lahey's web-based checker issue errors with
the above program. Is this simply a case of vendors trying to
be helpful?

--
Steve
http://troutmask.apl.washington.edu/~kargl/
.

Relevant Pages

  • Re: A few syntax questions
    ... I think putting them in the 'action-stmt' syntax rule ... If I were to redo the bnf from scratch, ... I guess that means that a standard conforming compiler is supposed to overflow. ... I am hoping that F2003 features will regain some respect for Fortran in CS departments,, and not just be coinsidered an old archaic language for old programs, but such strong support of archaic Fortran standards is a major reason why Fortran popularity continues to dwindle. ...
    (comp.lang.fortran)
  • Re: Form k = i + j and test for overflow.
    ... Last night you suggested I was forgetting that overflow violates ... the Fortran standard. ... test that wouldn't work on the most common of implementations. ... that conforms to the Fortran standard. ...
    (comp.lang.fortran)
  • Re: conditional compile for gFortran (GCC?): newbie question
    ... The official standard for a Fortran pre-processor is Part 3, "Conditional Compilation", informally known as CoCo. ... As I mentioned in a message in this thread yesterday, there are free implementations of CoCo available on the Internet. ... Obviously, CPP and its derivatives are widely used for Fortran, but I am not sure that the usage is so universal that it counts as a "de-facto standard", except perhaps in the Unix world. ... the capabilities and behavior of the Fortran pre-processor would be under the control of either the C or C++ committee. ...
    (comp.lang.fortran)
  • Re: FOR070.DAT files appearing
    ... IMPLICIT NONE has been Standard Fortran since 1993 when the Fortran 90 ... When F90 was approved, it became the ... I'd also challenge you to find a commercial Fortran 77 compiler ...
    (comp.os.vms)
  • Re: Any F2003 help translating C++ map syntax?
    ... >>part of the standard language, but makes a mockery of comparing ... > I sometimes miss convenient containers in the standard Fortran. ... That means that the standard STL might not be as ... > a hash table, if I remember correctly. ...
    (comp.lang.fortran)