philnash@programming.dev to Programming@programming.devEnglish · 9 months agoA comprehensive guide to the dangers of Regular Expressions in JavaScriptwww.sonarsource.comexternal-linkmessage-square15fedilinkarrow-up1107arrow-down12cross-posted to: regex@programming.devjavascript@programming.dev
arrow-up1105arrow-down1external-linkA comprehensive guide to the dangers of Regular Expressions in JavaScriptwww.sonarsource.comphilnash@programming.dev to Programming@programming.devEnglish · 9 months agomessage-square15fedilinkcross-posted to: regex@programming.devjavascript@programming.dev
minus-squarephilnash@programming.devOPlinkfedilinkarrow-up5·9 months agoJavaScript’s regex engine isn’t the only one to have these problems. There certainly are other implementations, like Re2 and Rust’s implementation, that don’t have this issue. But they also lack some of the features of the JS implementation too.
minus-squaresebsch@discuss.tchncs.delinkfedilinkarrow-up1arrow-down4·9 months agoOk thanks for the clarification. I would argue, the gold standard of regex would be perlre or even re from python. I never heard one discouraging using them. Do you know sth I don’t?
minus-squareburntsushi@programming.devlinkfedilinkEnglisharrow-up3·9 months agoBoth Perl and Python use backtracking regex engines and are thus susceptible to similar problems as discussed in the OP.
JavaScript’s regex engine isn’t the only one to have these problems. There certainly are other implementations, like Re2 and Rust’s implementation, that don’t have this issue. But they also lack some of the features of the JS implementation too.
Ok thanks for the clarification.
I would argue, the gold standard of regex would be perlre or even re from python. I never heard one discouraging using them. Do you know sth I don’t?
Both Perl and Python use backtracking regex engines and are thus susceptible to similar problems as discussed in the OP.