Daniel Micay on Twitter: "@ASFroz @thingskatedid Set it to regex mode instead of literal mode and use any arbitrary RE2 syntax. Quickly gives results via indexed searches. Here's an example for finding a bug of potential heap overflow bugs: https://t.co/bx6w0WSzTQ" / Twitter

oh for the confidence of somebody who has only used things, and never implemented them

A twitter comment, replying to @hanadusikova and myself: "Nah, regex is easy peasy lemon squeezy"

read image description

ALT

6

4

134

Replying to

Why not create a sane standard for regex instead of trying to match PCRE bug for bug? Knowing that perl regexen are Turing complete (because of eval).

2

Replying to

and

github.com/google/re2/blo Post series: swtch.com/~rsc/regexp/re swtch.com/~rsc/regexp/re swtch.com/~rsc/regexp/re swtch.com/~rsc/regexp/re This is the syntax for regular expressions in Gmail, Google Docs and other Google products. Go, Rust, etc. also use the same syntax / approach.

github.com

re2/syntax.txt at main · google/re2

RE2 is a fast, safe, thread-friendly alternative to backtracking regular expression engines like those used in PCRE, Perl, and Python. It is a C++ library. - re2/syntax.txt at main · google/re2

1

Replying to

and

RE2 approach only supports actual regular expressions (no backreferences or other horrors) and has an O(n) time complexity guarantee. Can also make an efficient search index. codesearch.debian.net is based on the indexing approach/code from the 4th post in that series. Try it.

1

Replying to

and

Set it to regex mode instead of literal mode and use any arbitrary RE2 syntax. Quickly gives results via indexed searches. Here's an example for finding a bug of potential heap overflow bugs: codesearch.debian.net/search?q=%28m%

2:35 PM · Apr 25, 2021Twitter Web App

Conversation