[bug #65962] [troff] want stack limit reduced to <=100

[Dave]

Follow-up Comment #3, bug #65962 (group groff):

This bug report does highlight one bit of inaccurate wording in the manual,
though.

[comment #1 comment #1:]
>  You can disable this protective measure, or
>  raise the limit, by setting the 'slimit' register.

In fact, you can also lower the limit.

$ cat slimit.roff
.de infinitely-recurse
\\n+[count]
.br
.infinitely-recurse
..
.nr count 0 1
.nr slimit 10
.infinitely-recurse
$ nroff slimit.roff | cat -s
troff:slimit:8: fatal error: input stack limit exceeded (probable infinite
loop)
1
2
3
4
5
6
7
8





___

Reply to this item at:

  

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


signature.asc
Description: PGP signature

[bug #65962] [troff] want stack limit reduced to <=100

[Dave]

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:

  

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


signature.asc
Description: PGP signature

[bug #65962] [troff] want stack limit reduced to <=100

[G. Branden Robinson]

Update of bug #65962 (group groff):

 Summary: input.cpp: reduce stack limit to <=100 => [troff]
want stack limit reduced to <=100


___

Reply to this item at:

  

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


signature.asc
Description: PGP signature