For now, I guess, you have two choices: you can escape to BoostBook markup and hand-highlight your code (I know, not too pretty), or you can wait just a little bit longer (there's no telling how long, though :( ).
Ah, OK I'll try escaping to XML, it's going to be tricky though as I want the text to contain a link. Still at least putting it inside a [def ... ] really helps: a very nice feature, but am I correct in thinking that macro expansion is not recursive?
Yes, you are. There's still another pitfall with the current implementation of macros and that is that they're not expanded in all contexts.
That said, another feature soon to be added is a separate preprocessing fase, that'll add more power and flexibility to the current macro system...
Here's a peek at the features being discussed:
* support for including external files (quickbook or code) status: James Fowler implemented, not in CVS.
Now that really would help me: so far I've only converted a half dozen type traits classes to quickbook (just playing with the formatting and layout at present), and the quickbook file is already getting a bit unmanageable. Once you get more than a few sections it gets hard to see where you are in the document, especially if they're nested within each other. A list of includes would be much easier to organise IMO.
Any chance of this one going into cvs soon?
Chances are high, I'd say... ;-)
Regards,
Jo�o
------------------------------------------------------- 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
