Jeff Garland wrote: > Joel de Guzman wrote: > >>> Or is this already possible with the template mechanism in some other >>> way? >> That's a perfect job for Python! :) I guess we should provide a >> boost python wrapper support for accessing the parser state info. >> This is Dave's wish list and I intend to pursue it along these >> lines. Python will have access to the "collectors", the (soon >> to be) "code stacks", filenames, symbol tables, etc. Then, in >> Quickbook, we can pass info to and from Python. > > Sorry to be a stick in the mud, but please don't increase the Quickbook > tool chain by adding Python to perform basic functions that don't > require it now.
Understood. As I see it, the basic std.qbk library should not require any scripting. I think there should be a way to enable scripting only when needed. IOTW, the user should not pay for things s/he does not need. With that restriction, templates should still simplify quickbook code to about 10-20% its current size. Pardon me if I wasn't clear with my reply to Dan. The [heading] markup will not be a template (again, basic std.qbk library should not require any scripting). What I meant is that if someone wants to add some user- markup that does something similar to [heading], it would (as I imagine) have to be through a scripting interface. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net _______________________________________________ Boost-docs mailing list [email protected] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
