Daniel James wrote:
James Fowler wrote:
Macro expansion doesn't work in the section title. Maybe this just
never worked, as it seems unlikely that anything you did would break
that but leave it working for headings and normal (not highlighted
source) content. Or maybe I missed something merging your changes. Can
you see if you get the same results?
It also gets skipped inside string literals and comments within
highlighted source code. I think you had already mentioned this
somewhere.
It would also be nice to be use macros like this:
[def __boost__ @http://www.boost.org]
Some text that mentions [__boost__ Boost], but then
writes it as [__boost__ the Boost Libraries].
You mean:
[def __boost__ [EMAIL PROTECTED]://www.boost.org]]
Some text that mentions [__boost__ the Boost Libraries], but then
writes it as [EMAIL PROTECTED]://www.boost.org the Boost Libraries].
? IOTW, macro expansion in markups?
Hmmm... I'm not sure, but, QuickBook is a single pass parser.
This might require 2 stage parsing. All of the above will be
possible by having a first preprocessing pass where all
macros (and possibly comments) are parsed and expanded.
Indeed, as it is now, macros are expanded only in certain
contexts (see rule common in the quickbook grammar). We
can add more where needed, or, simply do a pre-processing
stage. Thoughts? Now that we're having more stuff like
includes, perhaps it's a good idea to separate the preprocessing?
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
