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-May/053387.html below:

[Python-Dev] Pre-PEP: Unifying try-except and try-finally

[Python-Dev] Pre-PEP: Unifying try-except and try-finally [Python-Dev] Pre-PEP: Unifying try-except and try-finallyMichael Hudson mwh at python.net
Thu May 5 10:10:17 CEST 2005
"Shane Holloway (IEEE)" <shane.holloway at ieee.org> writes:

> And per the PEP, I think the explaining that::
>
>      try:
>          A
>      except:
>          B
>      else:
>          C
>      finally:
>          D
>
> is *exactly* equivalent to::
>
>      try:
>          try:
>              A
>          except:
>              B
>          else:
>              C
>      finally:
>          D
>
> Resolved all the questions about control flow for me.

Well, yes, that makes sense, but also raises a small "and the point
is...?" flag in my head.

Cheers,
mwh

-- 
  This is the fixed point problem again; since all some implementors
  do is implement the compiler and libraries for compiler writing, the
  language becomes good at writing compilers and not much else!
                                 -- Brian Rogoff, comp.lang.functional
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