Boost logo

Boost :

From: Markus Werle (numerical.simulation_at_[hidden])
Date: 2003-11-25 05:36:49


I am wading through the docs for library submitters
trying to find my way through the formal aspects of
proposing boost::etl (a redesigned version of Daixtrose).

Actually many points are clear and easy to follow,
but some remain that I'd like to have some help with:

While boost only requires
"The format for documentation should be HTML"
there is some more recommendation I'd like to follow,
especially the stuff below

My question: is there an easy way to achieve
an approximately conformant way to build the
docs _easily_?

Which tools or toolchain do you use, such that you
do not have to worry about formatting issues too much?
Is there a doxygen-based solution?
boost::spirit docs were made out of a wiki, which is
a very attractive approach, too, since it can grow slowly.

Which tools do you recommend?
Which pages at boost have I overlooked?

I am sitting in front of a linux box, so the
choices are pretty large. Any guide appreciated.

best regards,


P.S.: Not much hope, but: anyone with a tool which
"boostifies" source code such that it supports
the naming convention? SomeThing that changes to some_thing
and makes all template args Uppercase, etc ...

Build your own Expression Template Library with Daixtrose!

Boost list run by bdawes at, gregod at, cpdaniel at, john at