John Maddock wrote:
Joel de Guzman wrote:
So... I added a 'cinclude' tag (standing for code include) to quickbook which, given a file, includes it in the documentation marked up (and colored!) appropriately. The implementation is attached. It can very well be flawed as it is basically a copy&paste of other parts of the code, but so far seems to work.
Any chance this -- or something similar -- can be integrated? Certainly. I might need to ask for some more cinclude related features. Are you willing to do some more coding? Please email me.
Just a thought, but would it be better to make [include ] a phrase level element so it can include code or whatever, otherwise we'll end up with [cinclude ] and [pyinclude ] and [terminal_include ] and...... etc.
Phrases cannot include block-level elements, so if you want to be able to [include] another .qbk file which contains blocks, [include] cannot be a phrase. I would favor making [include] smarter, perhaps checking the extension of the file and acting appropriately. -- Eric Niebler Boost Consulting www.boost-consulting.com