David Abrahams wrote: > I'm wondering about the appropriateness of using Spirit for the > QuickBook parser. Even on a fast machine, the QuickBook interpreter > takes a *long* time to compile (with GCC 4.0.3, even in release mode). > > That's got to make it hard to work on QuickBook. As cool as Spirit > is, I know the same job could be done with Python code with no > appreciable parsing slowdown, and effectively zero compilation time.
Personally I have no problems with QuickBook being in C++. A non-"appreciable" slowdown might be fine for the uses you are thinking of, but some uses I want to put QuickBook to a small slowdown will be appreciable. What really aggravates me about the doc chain is the boostbook+docbook+xslt stage. It's horrible slow and extremely fragile. I'm lucky if I can run the doc translation without crashing xsltproc. And I have never been able to run the translations without a large number of errors or warnings. As I've mentioned to Joel, privately, what I really want is to go straight from QuickBook to XHTML. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo ------------------------------------------------------------------------- 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 _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
