> This is something that I have been wanting to try out for a long time.
> It makes the binary ~5Kb larger, and makes the memory footprint, when
> the Userguide is loaded ~300Kb smaller.
I have not compiled it and I am obviously blind: Where does the change
come from?
> Comments?
It's not my ballpark, but anyway: These half-page-chunks like
+ tmp.align = pp.param->align;
+ // tmp.labelwidthstring = pp.params.labelwidthstring;
+ tmp.line_bottom = pp.param->line_bottom;
+ tmp.pagebreak_bottom = pp.param->pagebreak_bottom;
+ tmp.added_space_bottom = pp.param->added_space_bottom;
+ tmp.line_top = pp.param->line_top;
+ tmp.pagebreak_top = pp.param->pagebreak_top;
+ tmp.added_space_top = pp.param->added_space_top;
+ tmp.spacing = pp.param->spacing;
+ tmp.pextra_type = pp.param->pextra_type;
+ tmp.pextra_width = pp.param->pextra_width;
+ tmp.pextra_widthp = pp.param->pextra_widthp;
+ tmp.pextra_alignment = pp.param->pextra_alignment;
+ tmp.pextra_hfill = pp.param->pextra_hfill;
+ tmp.pextra_start_minipage = pp.param->pextra_start_minipage;
+ tmp.noindent = pp.param->noindent;
+ tmp.depth = pp.param->depth;
make me wonder whether this should be encapsulated in an extra structure.
Of course, such an structure could be the second step in a second patch...
--------
> (I think some small mathed stuff sneaked in...)
std::cerr << std::comment(smallPatches) << std::endl;
abort();
Andre'
--
André Pönitz ........................................ [EMAIL PROTECTED]
