try..catch..finally?

[Michael Hudson]

Irmen de Jong <irmen at NOSPAMREMOVETHISxs4all.nl> writes:

> Mark McEahern wrote:
> > not that i knew this from first hand experience--that's what google's for
> > <wink>--but python did have a try-except-finally before the 1.0 release.
> > you can read all about it here:
> > http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=3967d908.363887342%4
> > 0news.online.no
> > // m
> 
> Heh, I didn't know. I've boarded the ship at release 1.2 :-)
> So I guess the answer to my question is AMBIGUITY.
> A separate try..finally around the other try block is unambiguous,
> in contrast to the try..catch..finally construct.

Yeah, just get used to functions that start

    try:
        try:
            try:

I have (see some functions in python_reader.py from pyrepl for
examples).

Cheers,
M.

-- 
  please realize that the Common  Lisp community is more than 40
  years old.  collectively, the community has already been where
  every clueless newbie  will be going for the next three years.
  so relax, please.                     -- Erik Naggum, comp.lang.lisp