On Tuesday 04 February 2003 07:05 pm, Beman Dawes wrote:
> I'm a little afraid to comment on specific optimizations, but the general
> problem you describe of taking "up at least 20x the real estate" is a
> serious one with a lot of the generated documentation I've seen, so I think
> if you can optimize away unneeded indirections it will help acceptance.
>
> While your disadvantages might be important in some contexts (like the C++
> Standard) they don't seem important in the context of Boost documentation.
> OTOH, the advantages seem very real and worthwhile to me.
>
> --Beman
I missed one other disadvantage: the compact enumerations (or anything else
that may be displayed more compactly) will not have associated man pages.
I think it is safe to say that there may be some circumstances where we would
not want the space optimization for enumerations (or functions), but in most
circumstances it will be worth saving a few trees or electrons. I've added a
stylesheet parameter "boost.compact.enum" that determines whether the
optimization will take place or not. It will default to '1' (true), but can
be turned off on the command line (for xsltproc)
--stringparam boost.compact.enum 0
I'll do the same for functions when I get to them.
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
