On Wed, Aug 24, 2005 at 09:45:16AM +0000, Thorsten Glaser wrote: > http://gcc.gnu.org/gcc-4.1/changes.html > > Terminal: XFree86(R) 4.5.0 xterm at 113x42; GNU screen with permanent > status bar inside (leaving 113x41 for lynx). > > [...] > if (d) > > { > > foo (&b, &c); > > a = b + c; > > } > > printf ("%d\n", a); > > } > > The a = b + c can be sunk to right before the printf. > Normal code sinking will not do thi ^^^^^^^ The extra blanks are from the <pre> section above, e.g.,
if (d) { foo (&b, &c); a = b + c; } printf ("%d\n", a); } </pre> The <code>a = b + c</code> can be sunk to right before the <code>printf</code>. Normal code sinking will not do this, it will sink the first one above into the else-branch of the conditional Though a quick check adding a <br> or <p> after the </pre> doesn't help. Removing the blanks does. This isn't a new problem. Comparing with IE, I see that it puts out the blanks, but puts a carriage return after them. Opera is doing the same thing. > it will sink the first one above into the else-branch of the > conditional jump, which still gives > you two copies of the code. > > [...] > > I see this quite often, some things are just outside the screen; > for example, if I had not had "links and form fields are numbered" > I'd not seen the login button of a page once... > > //mirabile > -- > I believe no one can invent an algorithm. One just happens to hit upon it > when God enlightens him. Or only God invents algorithms, we merely copy them. > If you don't believe in God, just consider God as Nature if you won't deny > existence. -- Coywolf Qi Hunt > > > _______________________________________________ > Lynx-dev mailing list > Lynx-dev@nongnu.org > http://lists.nongnu.org/mailman/listinfo/lynx-dev -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net _______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev