Follow-up Comment #6, bug #68908 (group groff):

[comment #4 comment #4:]
> In a dirty build environment, _anything_ might go wrong. 
> One can inject errors into the source code in countless ways.

You're right; I needed to clarify that none of my changes touched any C++
code.  In fact, had I modified even a single character of C++ code, I wouldn't
have opened this bug report until backing that change out.  I've made two
changes in the entire tree:

* I've changed some comments in one .tmac file (part of mucking about with bug
#62814) that only nroff uses.
* I've modified "configure" to always set groff_use_tex=no, which affects
which documentation gets built.

If either of these two changes can alter the formatter's behavior, that's a
more serious bug than I suspected.

> the only way we can have confidence in the result is
> to run "make check" afterwards.

============================================================================
Testsuite summary for GNU roff 1.25.0-modified
============================================================================
# TOTAL: 400
# PASS:  388
# SKIP:  7
# XFAIL: 5
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

This tells us there's no regression test for \n[.Y] being numeric.

[comment #5 comment #5:]
> If I meant for `.Y` to become "string-valued",
> I would have (assuming I kept my wits about me)
> committed a documentation change saying so.

I assumed so, thus assumed the change was accidental, thus characterized it as
a regression.  My initial report would have been different had it been a
documented change I disagreed with.

> In contrast, if you come up with a defect that permits
> non-numeric content into the `.Y` register in a "clean"
> working copy, I'm intensely interested to know about it--

Is a working copy that alters no C++ code clean enough?


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to