Big example:
pygame, event proccessing loop running. the user clicks "Quit", you do
break 2.
psuedocode:
while True:
    for event in pygame.events.get():
        if event.type==pygame.QUIT:
            break 2

james

On Sun, Oct 20, 2013 at 2:36 PM, Martin Matusiak <report@bugs.python.org>wrote:

>
> Martin Matusiak added the comment:
>
> I see one potential problem with this, namely that refactoring code that
> contains "break n" statements would become more error prone whenever the
> depth of the code block gets modified. So if you had something like:
>
> for i in range(10):
>     for j in range(10):
>         for k in range(10):
>             if cond:
>                 break 2
>
> And then you decided to remove the middle loop (on j), the break 2 would
> send you to the top level, whereas you might have meant for it to break to
> the first level, inside the loop on i.
>
> This is a micro example, of course, but if you imagine the bodies of these
> loops being quite long then it could get complicated fast.
>
> ----------
> components: +Interpreter Core
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue19318>
> _______________________________________
>