[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #65962] [troff] want stack limit reduced to <=100
From: |
Dave |
Subject: |
[bug #65962] [troff] want stack limit reduced to <=100 |
Date: |
Mon, 8 Jul 2024 08:31:47 -0400 (EDT) |
Follow-up Comment #2, bug #65962 (group groff):
Since the value is user-configurable, and since the reason for the default
_is_ documented (and reasonable for the reasons Branden mentioned), I agree it
shouldn't be changed.
But the source code does lack a comment where DEFAULT_INPUT_STACK_LIMIT is
defined citing the user documentation that addresses this limit. I'm not sure
how important this is: _most_ users will look at user documentation before
browsing source code. But there's a lot of user documentation, and some
details might not stick in one's brain, and a short comment here pointing to
the relevant part of the manual might be useful to future developers who have
spent fewer years polishing the manual than Branden has.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65962>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #65962] input.cpp: reduce stack limit to <=100, Bjarni Ingi Gislason, 2024/07/07
- [bug #65962] input.cpp: reduce stack limit to <=100, G. Branden Robinson, 2024/07/07
- [bug #65962] [troff] want stack limit reduced to <=100, G. Branden Robinson, 2024/07/07
- [bug #65962] [troff] want stack limit reduced to <=100,
Dave <=
- [bug #65962] [troff] want stack limit reduced to <=100, Dave, 2024/07/08
- [bug #65962] [troff] describe use of `slimit` register better, G. Branden Robinson, 2024/07/09
- [bug #65962] [troff] describe use of `slimit` register better, G. Branden Robinson, 2024/07/10