[bug #66233] ./nroff in "master"/build uses the 'nroff' in the $PATH

[Dave]

Update of bug #66233 (group groff):

                  Status:               Need Info => Invalid                
             Assigned to:                    None => barx                   
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #7:

[comment #6 comment #6:]
>  I have resolved the issue myself by creating a shell script.

Excellent news!  Closing.

> Also the "tmac files" where upstream forces the processors to repeat
> removing comments each times the files are read (Sisyphean work).

You're referring to work done by machines, which on today's hardware (and
honestly even on the hardware of 20 years ago that I still use) takes
negligible time, whereas removing the comments from shipped tmac files
needlessly obfuscates code for humans, whose time ought to be valued more than
that of CPUs.

In any case, these arguments have been hashed out in plenty of discussions
cited in the opening remarks of bug #55091.  If you can cite human-noticeable
differences in execution times between stripped and unstripped versions of any
macro files shipped by groff, please post those metrics in #55091, and the
decision made there three years ago can be reconsidered.  Otherwise, it's
impossible to take seriously your characterization of the extra work done by
groff's parser as "Sisyphean."  It's simple and repetitive work, the kind that
CPUs are very good and very efficient at.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66233>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

signature.asc
Description: PGP signature