* christopher diggins <cdiggins@videotron.ca> [2004-12-30 15:00]:

I am nearly finished a public domain C++ to HTML tool with syntax coloring.

The pretty printer recognizes and colors keywords, identifiers, string literal, character literals, number literals, macros and comments. It does so by using <span class="xxx"></span> tags around the elements. This means that italics / style / coloring can be controlled by a separate CSS file.

There are some future enhancements which could be interesting as well such as:

- automated hyper-linking of #include directives - javsascript open / close of code blocks { }

See? Look how people think of their applications in terms of *documents* these days. -- Alan Gutierrez - alan@engrm.com

christopher diggins wrote:

I am nearly finished a public domain C++ to HTML tool with syntax coloring. This is primarily intended as a demonstration of the YARD parser, but with practicial applications. I am wondering if anyone in the Boost community be interested in using the tool for sprucing up the code examples for the documentation to their libraries?

We already have something like that built into quickdoc/quickbook, which is Spirit-based. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com

christopher diggins wrote:

I am nearly finished a public domain C++ to HTML tool with syntax coloring. This is primarily intended as a demonstration of the YARD parser, but with practicial applications. I am wondering if anyone in the Boost community be interested in using the tool for sprucing up the code examples for the documentation to their libraries?

how does it compare to 'enscript' ? Regards, Stefan

-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of christopher diggins Sent: Thursday, December 30, 2004 12:41 PM To: Boost mailing list Subject: [boost] Anyone Interested in a C++ to HTML pretty printer?

I am nearly finished a public domain C++ to HTML tool with syntax coloring. This is primarily intended as a demonstration of the YARD parser, but with practicial applications. I am wondering if anyone in the Boost community be interested in using the tool for sprucing up the code examples for the documentation to their libraries?

The pretty printer recognizes and colors keywords, identifiers, string literal, character literals, number literals, macros and comments. It does so by using <span class="xxx"></span> tags around the elements. This means that italics / style / coloring can be controlled by a separate CSS file.

There are some future enhancements which could be interesting as well such as: - automated hyper-linking of #include directives - javsascript open / close of code blocks { }

Anyone interested?

Sure, that sort of thing is always useful, when well done. Have you considered leveraging the codebase to a straight C++ formatter? There really isn't one out there that's up to the task. I've been hacking GNU Indent for years to get something that sort of handles C++ and has the options I like; be nice to actually have a good free product out there that's designed to handle C++ with a good spread of options. If you had any interest, I could send you my annotated option file for Indent (obviously, I can't send the code, since it's copy-lefted). But the option file would show what's present (including some things that aren't in Indent's docs) and what I thought worth adding. Or not, if you prefer; I'm perfectly aware of the magnitude of such a piece of code. <g> Reid