[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [groff] Changing A Defined String
From: |
Tadziu Hoffmann |
Subject: |
Re: [groff] Changing A Defined String |
Date: |
Sat, 27 Jan 2018 22:27:11 +0100 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
> But I don't think that eliminates the macro call stack
> growing on tail recursion, like dc(1) does for example?
True, groff does not have an optimization for tail recursion,
so the input stack will fill up even in this case.
> I see groff's info says «Note that the number of available
> recursion levels is set to 1000 (this is a compile-time
> constant value of 'gtroff')».
I think what is meant is that the default value is
a compile-time constant. You can actually set the
register "slimit" to a higher value at runtime
if you need a larger stack.
- [groff] Changing A Defined String, Robert Thorsby, 2018/01/24
- Re: [groff] Changing A Defined String, Ralph Corderoy, 2018/01/25
- Re: [groff] Changing A Defined String, Steffen Nurpmeso, 2018/01/25
- Re: [groff] Changing A Defined String, Tadziu Hoffmann, 2018/01/25
- Re: [groff] Changing A Defined String, Robert Thorsby, 2018/01/25
- Re: [groff] Changing A Defined String, Tadziu Hoffmann, 2018/01/27
- Re: [groff] Changing A Defined String, Steffen Nurpmeso, 2018/01/27
- Re: [groff] Changing A Defined String, Tadziu Hoffmann, 2018/01/27
- Re: [groff] Changing A Defined String, Steffen Nurpmeso, 2018/01/27
- Re: [groff] Changing A Defined String, Robert Thorsby, 2018/01/28
- Re: [groff] Changing A Defined String, Peter Schaffter, 2018/01/28
- Re: [groff] Changing A Defined String, Robert Thorsby, 2018/01/28