On 28 Mar 2002 at 9:43, Guido van Rossum wrote: [me, on requiring Exception as base class] > > Hmm. If the rule were (eventually) strictly > enforced, > could we get the C++-style "stack > allocated object > whose destructor releases the > resource" trick > working? > > (a) I'm not sure I like to make that semantics > official, since it's > hard to implement e.g. in Jython. Don't blame me - I told JimH he was wasting his time <wink>! > (b) I'm having another dense day. How would > requiring exceptions to inherit from Exception make > this easier? Well, I implicitly hand-waved on a couple steps, like a total revamp of the sys.exc_* stuff. Bleh. No, I guess there's no way around the fact that that dangling reference is either a blessing or a curse, and which it is depends on circumstances external to the system. > > (Which would allow killing off the recurrent "with" / > > "using" thread.) > > In c.l.py? I'm not aware of it. We just had one here. Started out on hygenic macros, but ended up on hiding finally clauses. -- Gordon http://www.mcmillan-inc.com/
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