I've been using s/[ ]+//g; which seems to work effectively on all the varied spacing it's run into. Sticking it into runrigs Bench test as CURIOUS it yields:
coreolynBenchmark: running CURIOUS, LEADING, LEADTRAIL, LTSAVE, SEXEGER, SINGL +E_RE, WHILE_RE, each for at least 5 CPU seconds... CURIOUS: 6 wallclock secs ( 5.42 usr + 0.00 sys = 5.42 CPU) @ 39 +780.44/s (n=215610) LEADING: 6 wallclock secs ( 5.29 usr + 0.00 sys = 5.29 CPU) @ 68 +400.00/s (n=361836) LEADTRAIL: 6 wallclock secs ( 5.21 usr + 0.00 sys = 5.21 CPU) @ 28 +325.53/s (n=147576) LTSAVE: 6 wallclock secs ( 5.32 usr + 0.00 sys = 5.32 CPU) @ 30 +798.68/s (n=163849) SEXEGER: 5 wallclock secs ( 5.28 usr + 0.00 sys = 5.28 CPU) @ 50 +426.89/s (n=266254) SINGLE_RE: 6 wallclock secs ( 5.31 usr + 0.00 sys = 5.31 CPU) @ 54 +235.40/s (n=287990) WHILE_RE: 7 wallclock secs ( 5.47 usr + 0.00 sys = 5.47 CPU) @ 34 +396.53/s (n=188149)
In reply to Re: japhy blabs about regexes (again)
by coreolyn
in thread japhy blabs about regexes (again)
by japhy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |