Thomas Guest wrote:
Creating the regexes is no easier than defining a new parser
Ahh regexes! That's the price for dynamic loading. A long time ago, in a galaxy far away, Spirit grammars and rules used to be defined from strings. Maybe someday, I'll resurrect that capability. Hmmm, I should do that with Spirit 2.
This is my main problem with the proposed extension: when I wanted to extend
QuickBook to cope with a new source mode, I chose to add a Spirit parser and
recompile. If I wanted to add yet another source mode, I'd probably find it
easier to create a new Spirit grammar for that mode than to get the regexes going.
Right. But in the future, it might be agood idea to provide pre-canned versions of the applications (I'd really like to see a one-shot installer that installs all required components to get BoostBook/QuickBook going). In this case, it's not a good idea to require compilation of c++ code. We want instant gratification and ease of use.
Need to work out where to put the built-in highlight scheme
Details please?
I just meant that the quickbook executable needs to locate (on start up) the built in syntax highlight scheme file. The user could extend this scheme by supplying their own scheme via the command line, or indeed by editing the default one. It's not really a problem...
Ah yes. Well, no opinion here. We're already using program options so this will be trivial.
Cheers, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
