On Mon, Oct 6, 2008 at 4:20 PM, Scott Blum <[EMAIL PROTECTED]> wrote: > How do you clean up dead refs in the entry method, which isn't part of any > class?
Good catch. It sounds like there is a more fundamental problem. The runAsync entry methods actually are included in a class. Thus, in some circumstances I saw these methods get cleaned twice and thus ending up with invalid method calls. Since the normal entry method is not part of a class, there's no simple solution for Pruner to do its cleaning up. To make the story consistent, what would you think of attaching the existing entry method to some class? The other arrangement looks awkward, because the runAsync entry methods are the result of generator runs. They're plain old static methods. -Lex --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
