Yes, I think we would want to. My point is that we also would want to run the non-instrumented code. I have to think there could be subtle downstream behavioral differences (e.g. compiler optimizations that do/don't happen) based on whether the stack trace code is generated. Thus, I'm saying we should test both.
On Thu, Jul 23, 2009 at 1:09 PM, BobV <b...@google.com> wrote: > > > Technically, wouldn't it just mean we should not pin down the value of > the > > deferred binding property that controls it? It would double the number of > > permutations, tho. > > But wouldn't we actually want to run the instrumented code, to make > sure that the instrumentation itself doesn't break something? > > -- > Bob Vawter > Google Web Toolkit Team > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
