use actually invalid regex when testing for error #28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using a bare curly brace is not a fatal error in a regular expression.
Instead, the regex is failing to be compiled because the code tests it
using a string eval like `eval "m{$_}"`. Instead, use a regular
expression that is fully invalid by using an unmatched square bracket.
Member
Author
|
The test failures here are caused by the new version of Pod::Simple. I'm looking into a fix for that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using a bare curly brace is not a fatal error in a regular expression. Instead, the regex is failing to be compiled because the code tests it using a string eval like
eval "m{$_}". Instead, use a regular expression that is fully invalid by using an unmatched square bracket.