Blogger

Delete comment from: Neal Gafter's blog

Anonymous said...

Neal, I have a comment regarding code generation for mutated local context. You generate synthetic class for boxed local context. All seems fine, but I still see the programmer expecting a life time for his local variable being equal to function invocation. In case the closure is used asynchronously you keep a reference to local context in a closure, that could be claimed a memory leak. Would it be better to nullify the field when the function returns and set a flag. And all accesses from a closure should check the flag and throw exception in case the function frame is already not there?

Eugene.

Nov 22, 2007, 4:28:00 AM


Posted to Closures Prototype Update and Extension Methods

Google apps
Main menu