[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #56499] adjacent trap behavior undocumented and probably undesirabl

From: G. Branden Robinson
Subject: [bug #56499] adjacent trap behavior undocumented and probably undesirable
Date: Sun, 18 Dec 2022 17:13:03 -0500 (EST)

Follow-up Comment #3, bug #56499 (project groff):

[comment #2 comment #2:]
> [comment #1 comment #1:]
> > ...I believe _wrongly assume_ that there will be only one next
> > trap to be sprung.
> Interesting that this logic error seems to have been made independently in
both AT&T troff and groff.  (Plan 9 and Heirloom, I believe, both branched
from AT&T source code; groff did not.)

That's correct as I understand it.  I wonder how neatroff behaves; it is also
independent (and maybe the only other *roff that is).

But I'm not too surprised that the flaw was independently arrived at...  _If_
I'm correct, then it avoids creating a new data structure or maintaining a
sub-quantum trap location pointer that is distinct from the vertical drawing
> Additionally, the last-trap-planted-wins behavior avoids the question of
what order multiple traps at the same position should be run in, or whether
there's even a guaranteed order.



Reply to this item at:


Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]