Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Regex rejects IsPrint when combined with another character-class property

未关闭
#1,556 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
perl
领域
compilers

调研方向

Start by reproducing the failure with the character-class patterns in the issue and running t/01.new.t, t/04.particles.t, t/05.contributor.t, and t/06.source.t on both the JVM and interpreter backends. Inspect the existing Unicode alias handling, especially the Is/is-prefix logic; done means IsPrint combined with \s is accepted and the affected tests pass on both backends.

由索引模型根据 Issue 内容生成。

描述

area:cpan-port area:regex area:unicode bug

Summary

XML-Atom-App v0.0.5 fails under PerlOnJava because the regex engine rejects the valid Perl Unicode property alias \p{IsPrint} when it is combined with \s in a character class.

Reproduction

These patterns behave inconsistently:

  • qr/[\p{IsPrint}]/ succeeds.

  • qr/^[\p{IsPrint}]*$/ succeeds.

  • qr/[\p{IsPrint}\s]/ fails.

  • qr/^[\p{IsPrint}\s]*$/ fails with:

    Unknown user-defined property name IsPrint in regex

The failure affects both the JVM and interpreter backends.

CPAN evidence

  • Distribution: XML-Atom-App v0.0.5
  • CPAN run: 20260928-091741-26386
  • Failing tests: t/01.new.t, t/04.particles.t, t/05.contributor.t, t/06.source.t
  • PerlOnJava result: 20/21 tests; 4/10 test programs failed
  • System Perl result: all 56 upstream tests passed

The failing module code uses:

/^[\\p{IsPrint}\\s]*$/

The same compatibility failure appeared in earlier CPAN reports, including the 2026-08-26 and 2026-09-10 report runs.

Related work

Existing Unicode alias handling strips the Is/is prefix, and prior work addressed isAlpha-style aliases. This reproducer shows a remaining context-sensitive failure when the alias is followed by another property escape in the same character class.

主要语言
Perl
星标
64
派生
6
平均合并
4 小时 42 分钟
30 天内合并 PR
182

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fglock/PerlOnJava 的其他 Issue

查看 fglock/PerlOnJava 的全部 Issue

相似的 Issue

更多 Perl Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。