Joel de Guzman wrote:
At any rate, while it is easy to just shut off the post-processor as Eric is probably doing now, please, please don't. It is our only ticket to true regression testing. Without regressions, there will always be this nagging sense of insecurity (well, at least for me). Quickbook came from being a spirit demo, to being a real usable tool. I want it to be as robust as possible. Please forgive the inconveniences in the interim.
Aside from pretty-printing and regression testing, I think the post-processor could also be put to use to other ends.
For instance, EOL normalization could easily be done in the post-processor. QuickBook's handling of EOLs is currently broken for some inputs, I'm gathering test cases and looking at the issues.
I'm sure there are other things that could be done here. In the end, it is just another part of the app and there is no reason for cutting it out. If it's breaking things, then it's just more bugs we'll have to figure.
Regards, João ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
