Re: Why no named case statements?

[Britt <britt.snodgrass@gmail.com>]

On Sep 6, 7:44 am, Robert A Duff <bobd...@shell01.TheWorld.com> wrote:
> "Dmitry A. Kazakov" <mail...@dmitry-kazakov.de> writes:
>
> > Ada has labels:
>
> > <<Decide_This>>
> >    case Some_Variable is
> >        ...
> >    end case;
>
> > <<Decide_That>>
> >    if Whatever then
> >       ...
> >    end if:
>
> I prefer comments:
>
>    -- Decide this.
>    case Some_Variable is
>        ...
>    end case;
>
>    -- Decide that.
>    if Whatever then
>       ...
>    end if:
>
> To me, a label is a warning that gotos are lurking around the place.

Labels are also useful as breakpoint targets if the compiler produces
associated symbolic information that can then be used by the
debugger.  Using labels for this purpose is much better (more
maintainable) than breaking on line numbers.  Such permanent
breakpoints are sometimes useful in formal white-box test procedures.
SPARK was recently changed to allow  use of Ada labels for this
purpose (breakpoints, not gotos), and the GNATPP pretty-printer now
has a new switch to format Ada labels on separate lines (as shown in
Dmitry's example).

The responses to my original question have been informative.  I think
I would still like for the next revision of Ada to allow a name on any
multi-line construct that closes with an end keyword.  This would make
the language more symmetric, I think.  It would also be useful if Ada
IDEs included both names and labels in their outline view to
facilitate source code navigation.

- Britt