4 ms·
A couple of the image links are broken. Try http://pdos.csail.mit.edu/~rsc/regexp-img/script_Greek.png http://pdos.csail.mit.edu/~rsc/regexp-img/script_Greek.p
by ximeng 17y ago
A couple of the image links are broken. Try
http://pdos.csail.mit.edu/~rsc/regexp-img/script_Greek.png http://pdos.csail.mit.edu/~rsc/regexp-img/script_Greek.png
http://pdos.csail.mit.edu/~rsc/regexp-img/cat_Lu.png http://pdos.csail.mit.edu/~rsc/regexp-img/cat_Lu.png
for the trees used to match greek scripts and lower case letters respectively.
Another interesting article from the guy who wrote Google Code Search if I'm not mistaken.
- rsc 17y agoImage links fixed.
- ableal 17y agoThanks for great article, but I'd also suggest s/cacophany/cacophony/ (If theophany is "an appearance of a deity to man", 'cacophany' sounds like "shit happens" ;-)
- rsc 17y agoThat's probably an even more appropriate term for modern regular expression syntax, but you're right, it isn't the sense I was going for. Fixed, thanks.
- ableal 17y agoAs long as I'm picking nits, I'd also object to the final header being a 'Summary' - it's more a 'Conclusions'. My speed-reading summary (aka tl;dr): - Your RE2 implementation beats the snot out of sparring-partner PCRE, as graphically demonstrated in the tail end. - At the cost of leaving out some esoteric features, and a bit more memory (still small for current times). - Does Unicode. - Has automatically-generated tests (supplementing a small core of hand-written ones). - Leaves reader feeling like he saw a demo of fine precision engineering ;-)