Joel de Guzman wrote:
I took a peek at the code, and, alas... it's innevitable, we need to handle tabs. Take a peek at list_format_action, for example. The quickbook syntax relies on block layout (ala python) in certain places such as list handling. We can issue a warning, sure, but we'll still have to correctly handle them when they are present, otherwise, block formatting will go awry.
This might not be an issue, if it was working before. I think the only place affected by the changes for tab/space/newline handling is Thomas's syntax_highlight::highlight( ... ) function, which now calls the new detail::print_range_preserving_whitespace(...) instead of detail::print_range(...). This tweaks how we do the output - there should be zero change to the input content that list_format_action is parsing. Anything other than highlighted code should work the same way it always has. Unless, of course, I'm missing something besides my coffee this morning :)
- james
-- __________________________________________________________ James Fowler, Open Sea Consulting http://www.OpenSeaConsulting.com, Marietta, Georgia, USA Do C++ Right. http://www.OpenCpp.org, opening soon!
------------------------------------------------------- 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
