Should running a web-mode test case always turn on the emulated stack trace code?
You would get stack traces entries like: Unknown.bx(YourClass.java:1234) regardless of which browser you're on and the type of exception, Java-derived or native. The cost is code bloat: 64k versus 108k for the CoreSuite test to have both file names and line numbers. Just line numbers costs 96k and the stack alone is 80k. The latter two cases would be more useful if JUnitShell retained the symbol maps and deobfuscated the stack trace for you, but that's an orthogonal pass. -- Bob Vawter Google Web Toolkit Team --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
