I will raise some attention to this. -Daniel
Am 02.10.2012 um 22:45 schrieb Chris Lercher <[email protected]>: > Sorry, but definitely no. Admittedly, I've never actually encountered such a > GWT bug in my own code. But that's irrelevant. Imagine you're changing a > method temporarily to debug some code (in a way, that it always returns > true), and in compiled mode it will simply not do what you expect - you'll > search thousands of places before thinking that it could be a compiler bug. > > 1. Such bugs are avoidable. 2. It's a compiler's job to make sure you can > rely on the basics - everything builds upon that, and errors at that level > may amplify, leading to completely unpredictable results. This has nothing to > do with good coding on the GWT developer's side (BTW, unit tests are often > examples of intentional bad coding. What if they fail - or worse: pass - > unpredictably?) > > > > On Tuesday, October 2, 2012 7:21:47 PM UTC+2, jchimene wrote: > +1 on Manolo's point. > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/GkEDfwGo3PcJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
