On Nov 19, 2007 11:42 AM, apfelmus <<a href="mailto:apfelmus@quantentunnel.de">apfelmus@quantentunnel.de</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks. The interesting case of nested blocks still needs to be<br>specified, but with this description in mind and judging from the code,<br>I guess it behaves as follows: either a block fits entirely on the<br>remaining line (no line breaks inside), or it begins a new line.
</blockquote><div class="Ih2E3d"><br>Yeah, breakdist does not look inside a block when computing the break distance.<br> <br>> On the strictness annotations, my reasons for them are the usual ones,<br>> primarily to prevent memory leaks due to dragging, but a performance boost
<br>> is always welcome. At some point, I plan to profile the code with and<br>> without the annotations, and find out where they are needed.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
That seems excessive. Can you really prove that this will prevent space<br>leaks? I doubt that.</blockquote></div><br>Ooh, I think I overstated my case. I meant to say that for my application, there are just a few data structures, such that if data traceable from them is strictly evaluated, I'm pretty sure I will have no space leaks. Currently it's just an intuition, but when the application is mature, I'll profile and validate this intuition. All I know is it was dog slow without any annotations, and spaying them on the suspect data structures cured that problem. Only careful profiling will tell which of those annotations can be removed.
<br><br>John<br>