I hit a problem with a build compilation without line breaks when trying to make our unit tests. "for (a in b)" loops were corrupted to "for (a inb)" giving an error when trying to load the page of
"missing ; after for-loop initializer" I've tracked down the cause and documented some possible fixes at http://bugzilla.qooxdoo.org/show_bug.cgi?id=840 This is obviously a critical issue in that corrupted code can be generated. A question: why is the unit test compilation done without line breaks? Shouldn't that use the same compilation flags as the main application so that the unit tests are done with the same environment? Hugh ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
