> Would "always on" mean that it generates code even for browsers that have > native stack traces (i.e. FF)?
Yes, for the purpose of giving you consistency between browsers. > Generally, as much as I hate to say it, it seems we'd want variations of the > tests both with and without stack trace code, so that we don't inadvertently > break one mode or the other. It is much like "-draftCompile" in this > respect. That would imply that emulated stack traces would have to be triggered by a command-line switch or a Java environment property as opposed to deferred-binding rules. -- Bob Vawter Google Web Toolkit Team --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
