On Mon, 3 Feb 2003, Jeff Garland wrote:
> Yes, but even if we restrict the generated output to the reference section,
> I agree with Vladimir that we need to be able to exclude some things. That
> is, we might have some detail classes that we don't want picked up in the
> docs. But I think we can control this by using build processes and config
> settings.
Okay. So we'd like to have a way to say "this is an implementation detail,
don't document it" somewhere in the toolchain. It could easily be done
either as a BoostBook feature or as a feature of the Doxygen->BoostBook
translator.
> > By forcing developers to keep the reference material together, it forces them
> > (err, us) to keep the reference material consistent. My dream would be that
> > we could generate library proposals with just a few switches passed to the
> > XSL stylesheets :)
>
> Gee ,I hope you don't think this is a 'far-off dream' because I'm intending
> on doing just that!
>
> Jeff
I think it's entirely feasible to do this. We're just not there yet :)
Doug
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
