in reply to Re^13: Reusing a complex regexp in multiple spots, escaping the regexp
in thread Reusing a complex regexp in multiple spots, escaping the regexp

It's like complaining about state being buggy since it acts differently to my ...

Indeed, that's exactly what it is. Why it could be considered buggy in the case of "/o" though is that it's poorly documented, rarely desired, and very easy to miss when debugging because it's a single character often hidden away in the middle of or at the end of an expression, instead of a full keyword at the start of statement like state.

Hire me at Toby Ink Ltd or Join my OnlyFans
  • Comment on Re^14: Reusing a complex regexp in multiple spots, escaping the regexp
  • Download Code

Replies are listed 'Best First'.
Re^15: Reusing a complex regexp in multiple spots, escaping the regexp
by LanX (Saint) on Apr 17, 2026 at 14:11 UTC
    The poor and distributed¹ documentation is the problem

    And the way perldocs are often handled as witty prose resulting from group dynamics instead of being based on evidence (i.e. test cases).

    I don't think it's ever appropriate to flag a feature "buggy"

    • if there are unexpected side-effects a "warning" should be explained in a footnote.
    • if they are really "buggy", they should be disabled.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    see Wikisyntax for the Monastery

    ¹) perlop has far more than perlre and perlretut has only a "\o ... beyond the scope of this introduction" ...

[reply]

In Section Seekers of Perl Wisdom