[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34910: 27.0.50; Too much matching reentrancy
From: |
Mattias Engdegård |
Subject: |
bug#34910: 27.0.50; Too much matching reentrancy |
Date: |
Sat, 30 Mar 2019 14:05:50 +0100 |
30 mars 2019 kl. 13.55 skrev Stefan Monnier <monnier@IRO.UMontreal.CA>:
>
> It was probably just an oversight, because whether we're searching
> within strings or within buffers the same problems appear with \{N\}
> repetitions (where the counter is stored directly inside the
> regexp-byte-code) and with on-the-fly strength-reduction (where we
> replace some byte-code with cheaper ones (where applicable) on the first
> pass through the regexp).
Is the reentrancy just in preparation for future needs, or is it possible to
re-enter the regexp code right now?
If the latter, we may just as well fix the string case here and now; otherwise,
I'd like to close the bug.
- bug#34910: 27.0.50; Too much matching reentrancy, (continued)
- bug#34910: 27.0.50; Too much matching reentrancy, Mattias Engdegård, 2019/03/19
- bug#34910: 27.0.50; Too much matching reentrancy, Mattias Engdegård, 2019/03/19
- bug#34910: 27.0.50; Too much matching reentrancy, Eli Zaretskii, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy, Mattias Engdegård, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy, Daniel Colascione, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy, Stefan Monnier, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy,
Mattias Engdegård <=
- bug#34910: 27.0.50; Too much matching reentrancy, Eli Zaretskii, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy, Stefan Monnier, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy, Daniel Colascione, 2019/03/30
- bug#34910: 27.0.50; Too much matching reentrancy, Mattias Engdegård, 2019/03/30