Skip to content

Conversation

@karenetheridge
Copy link
Member

This is a follow-up to commit 865a14b, which added the double-escape which should fix the warning, but there was an error in the blead change that causes it to still warn, erroneously. Work around this by just using a normal quoted list.

This is a follow-up to commit 865a14b, which added the double-escape which
*should* fix the warning, but there was an error in the blead change that
causes it to still warn, erroneously. Work around this by just using a normal
quoted list.
@karenetheridge
Copy link
Member Author

The false positive in blead is fixed in Perl/perl5#23611, but it will be another month before this makes its way into a release, so the only remedy until then is the fix I provided here.

@haarg
Copy link
Member

haarg commented Aug 21, 2025

I don't think I want to make a change to support a bug in a single development release.

@karenetheridge
Copy link
Member Author

The alternative is letting everything downstream of it be broken for a month. This is either a minor or a major inconvenience depending on how much testing people are doing on blead releases.

@haarg
Copy link
Member

haarg commented Sep 26, 2025

With the release of perl 5.43.3 this isn't needed. Thanks.

@haarg haarg closed this Sep 26, 2025
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.

3 participants