Re: Long line of OR

On 12 Oct 2011, at 12:08 , Professional Software Engineering wrote:
> You may however see more of an improvement by optimizing your regexp:
> 
>> (a(a|psumo|dmin)|b(eni|smith)|c(andy|asa|f|pr)|d(b|bl|hosts)|fb|g(lue|ofobo)|hita|ic|l(lc|ogi)|micr|netf|ocb|p(lus|l)|r(smith|oot|cc|k|ocb)|s(cv|nap|pot|u)|t(or|ripa|wit)|v(365|m))
> 
> Readability takes a big dive though.

Readability is important, especially since the list changes every now and again.

> Again, youd need to run benchmarks - put recipes in a sandbox, run against a large corpus several times, omitting the longest and shortest times (owing to the effects of cache, etc), and would need to run it on a host which didn't have other demands on it.

OK, I was afraid I was forgetting something like maximum line length or something like that.

-- 
Advance and attack! Attack and destroy! Destroy and rejoice!