try..catch..finally?
Irmen de Jong
irmen at NOSPAMREMOVETHISxs4all.nl
Thu Jul 11 16:47:38 EDT 2002
More information about the Python-list mailing list
Thu Jul 11 16:47:38 EDT 2002
- Previous message (by thread): try..catch..finally?
- Next message (by thread): try..catch..finally?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. Thanks Irmen
- Previous message (by thread): try..catch..finally?
- Next message (by thread): try..catch..finally?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list