Programming

17001 readers

336 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

105

A comprehensive guide to the dangers of Regular Expressions in JavaScript (www.sonarsource.com)

submitted 11 months ago by philnash@programming.dev to c/programming@programming.dev

15 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] sebsch@discuss.tchncs.de -4 points 11 months ago (1 children)

Is there one thing not screwed up in this language? I mean it's regex, there are so many good implementations for it.

[–] philnash@programming.dev 5 points 11 months ago (1 children)

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.

[–] sebsch@discuss.tchncs.de -3 points 11 months ago (1 children)

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?

[–] burntsushi@programming.dev 3 points 11 months ago

Both Perl and Python use backtracking regex engines and are thus susceptible to similar problems as discussed in the OP.