> > 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?) >
Agree 100%: compiled code should behave the same than debug mode, and should match all java language specifications. But any gwt developer knows that the gwt compiler has a set of limitations which are widely admitted and documented (regex, number arithmetic, etc), I have spent a lot of time trying to figure out why some tests passed in dev and not in production though. So, the point here is what to do with the issue, IMO it should be fixed if possible, otherwise it should be documented or make the compiler print an error, but I wouldn't revert the optimization strategy. Related with the huge gwt issues list, I think that the gwt team should face them seriously (I hope this is a priority for the steering committee). - Manolo > > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
