Update of bug #60260 (group groff):
Status: None => Invalid
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #6:
Let us port the specimen in comment #0 to AT&T _troff_.
$ cat EXPERIMENTS/60260a.roff
.de XX
. tm --- XX called with '\\$1' ---
. ie '\\$1'a' .tm CASE a
. el .ie '\\$1'b' .tm CASE b
. el .ie '\\$1'c' .tm CASE c
. el .tm Got something else (\\$1)
..
.XX a
.XX b
.XX c
.XX d
...and observe the output of DWB 3.3 _nroff_, Heirloom Doctools _nroff_, and
GNU _nroff_.
$ ~/groff-stable/bin/nroff EXPERIMENTS/60260a.roff # 1.23.0
--- XX called with 'a' ---
CASE a
--- XX called with 'b' ---
CASE b
--- XX called with 'c' ---
CASE c
--- XX called with 'd' ---
Got something else (d)
$ cd ~/dwb && DWBHOME=. ./bin/nroff 60260a.roff
--- XX called with 'a' ---
CASE a
--- XX called with 'b' ---
CASE b
--- XX called with 'c' ---
CASE c
--- XX called with 'd' ---
Got something else (d)
$ cd ~/heirloom && ./bin/nroff 60260a.roff
--- XX called with 'a' ---
CASE a
--- XX called with 'b' ---
CASE b
--- XX called with 'c' ---
CASE c
--- XX called with 'd' ---
Got something else (d)
...and for grins, Solaris 10 _nroff_...
bash-3.2$ nroff 60260a.roff
--- XX called with 'a' ---
CASE a
--- XX called with 'b' ---
CASE b
--- XX called with 'c' ---
CASE c
--- XX called with 'd' ---
Got something else (d)
So none of these formatters exhibit distinguishable flow of control.
To the extent that this ticket claims an incompatibility between AT&T _troff_
and GNU _troff_, it is invalid.
To the extent that it claims that GNU _troff_'s `el` warning can be
misleading, I agree; but it is then a duplicate of bug #65474. That is indeed
a later-filed ticket, but it has a meatier discussion.
Jim Avera noted most of this 3 years ago in comment #1.
So I'm resolving this one as invalid.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60260>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
