Steven D'Aprano writes:
> On Wed, Jul 22, 2020 at 06:14:39AM +0300, Paul Sokolovsky wrote:
> > But no, loop executes, *or else* the following "else" block
> > executes ;-).
He means the loop *suite* executes (this includes "getting to" a break
statement or other control flow that leaves the lo
Mathew Elman writes:
> Frankly, saying that a part of a language that is frequently
> misunderstood, is *never* allowed to be improved is disappointing
> when the suggestion that it can be (somehow) has been so well
> received by everyone else.
The highly improbable is frequently well-receive
On 23/07/2020 16:24, Stephen J. Turnbull wrote:
Steven D'Aprano writes:
> On Wed, Jul 22, 2020 at 06:14:39AM +0300, Paul Sokolovsky wrote:
> > But no, loop executes, *or else* the following "else" block
> > executes ;-).
He means the loop *suite* executes (this includes "getting to" a b
On 23/07/2020 16:24, Stephen J. Turnbull wrote:
Steven D'Aprano writes:
> On Wed, Jul 22, 2020 at 06:14:39AM +0300, Paul Sokolovsky wrote:
> > But no, loop executes, *or else* the following "else" block
> > executes ;-).
He means the loop *suite* executes (this includes "getting to" a
