Re: code partitioning (was: Future with Ada)

["Nick Williams" <nickw@acm.org>]

Well, the reason for having labels on loops is fairly clear; to allow an
exit statement to exit from a loop other than the innermost enclosing one.
So there's obviously a concrete 'why' for loops - its not as clear for
blocks (although I can see that it might be nice to have a construct which
allows a new declarative region to be nameable).

On the other hand, allowing this for if and case statements sounds a lot
more like simple syntactic sugar. I don't really think it's sufficient to
say 'language construct A has this additional syntax; so why not B?', rather
the question should be 'why does language construct A have this additional
syntax, and does language construct B benefit from it in a consistent way?'.

Cheers,

Nick.

"Christoph Grein" <christoph.grein@eurocopter.com> wrote in message
news:mailman.1016084642.17231.comp.lang.ada@ada.eu.org...

> This is the only form I would like to see as a future syntax enhancement.
We
> already have this for loops and blocks, so why not for ifs and cases (and
> selects).
>
> We do not need weird new syntax rules.
>