On Sun Mar 31 06:33:17 2019, ANDK wrote:
Show quoted text
The test is using a variable-length lookbehind expecting it to die, for reasons not immediately clear - the placement suggests it may be attempting to verify that re-engine-Lua's unimport works, so perhaps this is something supported by the Lua engine.
The test will need to change. If it is indeed attempting to check something supported by Lua's engine but not Perl's, I guess Francois will need to find a different indicator. The perldelta entry gives clues to a couple of approaches:
Using a lookbehind assertion (like C<(?<=foo)> or C<(?<!bar)> previously
would generate an error and refuse to compile. Now it compiles (if the
maximum lookbehind is at most 255 characters), but raises a warning in
the new C<experimental::vlb> warnings category. This is to caution you
that the precise behavior is subject to change based on feedback from
use in the field.
.. so either the warning or the 255 limit may be suitable. But both of those may well change again in future releases, so it's possible an entirely different approach would be better, eg by using a regexp with an embedded code block.
Hope this helps,
Hugo
