Don’t underestimate grep-based code scanning

Re:Don’t underestimate grep-based code scanning by burntsushi on Wednesday August 07, 2019 @04:09PM (#20638392)

That's not true. They work just fine. Typically, substring search algorithms are implemented at the encoding level, e.g., on UTF-8 directly. If you just treat that as an alphabet of size 256, then algorithms like Boyer-Moore work out of the box.

But the skip-ahead stuff isn't the most important thing nowadays. The key is staying in the fast vectorized skip loop as long as possible.

[ Parent | on HN ]

Re:Don’t underestimate grep-based code scanning by jandrese on Wednesday August 07, 2019 @04:12PM (#20638424)

I noticed severe slowdowns when passing in the /u flag on my regexes, even with big fixed ASCII strings in the middle of the patterns. They were taking 10 times as long to complete.

[ Parent | on HN ]

Re:Don’t underestimate grep-based code scanning by burntsushi on Wednesday August 07, 2019 @04:43PM (#20638804)

That doesn't imply that things like Boyer-Moore suddenly stop being effective. Without more details (which regex engine? what regex? what corpus? which programming language?) it's impossible to state the cause, but it could be as simple as the regex engine not being smart enough to use a literal searcher in that case.

[ Parent | on HN ]

Re:Don’t underestimate grep-based code scanning by JetSpiegel on Wednesday August 07, 2019 @07:01PM (#20640108)

Since you don't want to toot your own horn, and you saved me many hours of not waiting for searches, I'll link to ripgrep here

https://github.com/BurntSushi/ripgrep

[ Parent | on HN ]