mjgardner, 3 months ago

@neustradamus #PCRE continues to be a misnomer; it’s a modified subset of #Perl #RegularExpressions with dozens of differences: https://pcre.org/current/doc/html/pcre2compat.html

It's not "(C)ompatible." Accept no substitutes: https://perldoc.perl.org/perlre

#PCRE2 #PerlIncompatibleRegularExpressions #RegularExpression #RegExes #RegExps #regex #regexp

mjgardner, 7 months ago

@vwbusguy @barubary
@Perl I’m glad https://mastodon.online/@vwbusguy/111212516938547685 works for you, but I feel pity for when you come back to it later.

It’s nothing to do with #Perl and everything to do with shitty #regex possible in almost any #programming language.

Though it’s true that Perl’s reputation took a lot of damage from shitty developers filling the world with shitty #regexes in their shitty Perl code. So you’re in a big group, albeit via #Ruby.

mjgardner, 10 months ago

@profoundlynerdy I don’t think other languages have “ripped off” #RakuLang #regexes and grammars. The point of a notional “RCRE” library would be to enable that.

mjgardner, 11 months ago

@malwareminigun @jernej__s #Perl has readability affordances for #regexes that nothing else can touch: https://perldoc.perl.org/perlre#%2Fx-and-%2Fxx

mjgardner, 1 year ago

@regehr @commodore @dev There is even a (low-severity, a/k/a “cruel”) #PerlCritic policy to discourage everything but $_, @_, $], and numbered #RegularExpression capture variables: https://metacpan.org/pod/Perl::Critic::Policy::Variables::ProhibitPunctuationVars

https://metacpan.org/pod/Perl::Critic::Policy::Variables::ProhibitMatchVars already protects you against the performance-sapping $`, $&, and $' match variables

And you can configure your own prohibited list with https://metacpan.org/pod/Perl::Critic::Policy::Variables::ProhibitEvilVariables

#Perl #RegEx #RegExp #RegExes #RegExps