Skip to content

Conversation

@khwilliamson
Copy link
Contributor

For an illegal group name in UTF-8, the pointer to the problematic character could be pointing to an incomplete character. because the code neglected to consider if the name was UTF-8 or not.

The description of what a legal name is had not been updated to include UTF-8 names.

  • This set of changes does not require a perldelta entry. The bug fix I believe is too minor to warrant one; and the documentation changes will shortly be subsumed by further ones that will provide a perldelta entry that would override this one

@jkeenan
Copy link
Contributor

jkeenan commented Oct 25, 2025

2 tests failing in t/re/reg_mesg.t.

This just fills out a couple of tests so that they don't prematurely
end.  That makes it clear that the eorror that does get shown isn't also
due to other mistakes in the test.
This was written before Unicode, and its wording does not accurately
extend beyond ASCII.

This commit clarifies the description.
I found this by reading the code.  Prior to this commit, the parse
pointer was advanced by one byte; it should be advanced by one
character.  As long as the the character was ASCII, things worked.

I looked through the regcomp.c source for other mis-use of the macro
changed by this commit; none were obvious.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants