> Yes, it's always good to look for other bugs in the same class as the > original bug. >
And it's also about refactoring (as you might know, I'm already thinking about a next-generation pretty-printer, and don't want to put unnecessary effort in the old code). > I hope you will request a corpus of code from people (perhaps under an NDA) > to test all the formatting stuff. I've only run one file through the > pretty-print and possibly other files will show up other problems. Obviously > it helps you to have as much different styles as possible to fix things up. > That's an interesting idea, I might think about that. In general I'm very much in favour of automated and regression tests. Not sure how to set this up for a pretty-printer and how to assess outcome, though. > Out of interest, what happens if you run a compressed qooxdoo file through > the pretty-printer? Does it come out nice and neat? > I don't know, I haven't tried ;-) =Thomas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
