A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-July/054733.html below:

[Python-Dev] Chaining try statements: eltry?

[Python-Dev] Chaining try statements: eltry? [Python-Dev] Chaining try statements: eltry?Facundo Batista facundobatista at gmail.com
Fri Jul 8 03:32:30 CEST 2005
On 7/7/05, Gustavo Niemeyer <gustavo at niemeyer.net> wrote:


> > Simplifying the basic control flow mechanisms is always good.
> [...]
> 
> Of course, it largely depends on what simplifying means to you.

If we lose the "else" in "for"s, we'd have to use a variable to mark
when we exit the normal way or we break it out.

Using another variable is something that complicates the reading of
the program: you see the new variable, have to discover to what it's
for, and to keep it in your mind while you follow the logic.

For me, simplifying means keeping the "else".

Just my Currency("0.02"), ;)

.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4