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



"Steven G. Kargl" <kargl@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:d4v9pv$1sk$1@xxxxxxxxxxxxxxxxxxxxxxxxxx

> I'd be interesting in your reasoning. AFAICT, the construct-name
> is local to the construct. For example, a EXIT or CYCLE in the 2nd
> loop of the example code that I posted will not branch to the
> end of the first loop.

You seem not to have noticed that Richard likes to use construct
names even when they aren't necessary, just so that he can tell
at a glance which control statements go with which construct.
Definitely a step in the direction towards self-documentation,
and I know from experience just how hard it can be to spot an
error caused by thinking a control statement refers to a
different construct than it actually does. Allowing multiple
constructs to have the same name erodes the effectiveness of
this self-checking feature.

--
write(*,*) transfer((/17.392111325966148d0,6.5794487871554595D-85, &
6.0134700243160014d-154/),(/'x'/)); end


.



Relevant Pages

  • Re: COBOL myth busted, index versus subscript (MF on HP)
    ... curious about an array without an index defined, ... So, Question, what is exit perform cycle? ... When I first ran the test, the null loop was empty. ...
    (comp.lang.cobol)
  • Re: dumb question #1 re: DO loops
    ... an exit from the loop would be: ... or, even better, in my personal opinion, ... if <0) cycle the_do_loop ...
    (comp.lang.fortran)
  • Re: uniqueness of {if,do,case}-construct-name
    ... >> end of the first loop. ... > at a glance which control statements go with which construct. ... do-construct-name on the 2nd loop as an error. ... whether the code I originally posted conforms to the standard, ...
    (comp.lang.fortran)
  • Re: Exit in Fortran 90/95
    ... victor wrote: ... After exit (or cycle) you can put a do construct name. ... A plain exit would just exit the loop it is in ...
    (comp.lang.fortran)
  • Re: A question on for loop
    ... control statements. ... would still be, IMHO, misuse of the "intent" of such a type of loop ...
    (comp.lang.c)