On Fri, May 29, 2009 at 6:10 PM, <[email protected]> wrote: > Besides Scott's suggestion, I have one more thing to add. For any method > that mutates the Date, wouldn't it be more useful to call > [email protected]::checkJsDate()(); both when entering and exiting > the method? Then, we can get a stack trace of the problem code > immediately. >
If you look, the mutators only change the state of the Date object, not the reference itself. Also, the jsdate is set in every constructor path to a Date instance, so the only way it could be null is if it is getting cleared externally (or perhaps there was a serialization problem and this instance came from the server in an RPC response). So I don't think there is anything to gain by checking it after a mutator that can't possibly change the jsdate reference. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
