use Regexp::Common;
print $RE{URI}, $\;
[download]

Im just curious, did you look at that regex before you suggested it or did you just guess that it might be appropriate?

---
demerphq

I saw it in a talk by Abigail during OSDC. Here's the slide. But I had to look again to make sure it had alternations.

(?!.*(?:customer relationship|enterprise resource planning|e-business|
+int(?:ernationa)?l data management|systems, architecture|ww|is projec
+ts))
[download]

Thanks. This was interesting. I ended up playing around with words.t and discovered a slight bug that isn't exposed by this test. The regex /foobar|foo/ is equivelent to /foo(?:bar)?/ the regex /foo|foobar/ is equivelent to the regex /foo(?:|bar)/. Regex::PreSuf along with similar modules like Regexp::Assemble and Regexp::List will generate /foo(?:bar)?/ for both. Eg:

G:\cblead2\win32>perl -e "print $& if 'foobar'=~/foo|foobar/"
foo
G:\cblead2\win32>perl -e "print $& if 'foobar'=~/foo(?:|bar)/"
foo
G:\cblead2\win32>perl -e "print $& if 'foobar'=~/foobar|foo/"
foobar
G:\cblead2\win32>perl -e "print $& if 'foobar'=~/foo(?:bar)?/"
foobar
[download]

Unfortunately this makes them not entirely suitable for my needs. But it has proved interesting using them. :-)

Read more... warning wide code (5 kB)
---
demerphq

Here's one that i use to do some matching on HP-UX iostat output :

  m/^
    (
    NANQ|INF|NANS|   # Possible non numerics
    \d+              # a number ...
    (?:[,\.]\d+)?     # ... with an optional decimal part
    )                # memorise the value of : tin .

    \s+

    (
    NANQ|INF|NANS|   # The same one
    \d+              
    (?:[,\.]\d+)?     
    )                # memorise the value of : tout .

    \s+
                                                
    (?:[\d\s\.,]|NANQ|INF|NANS)+       # Rest of the line . 

$/x
[download]

Another one :

s/^\d\d:\d\d:\d\d\s*(?:CPU|INTR)\s*//
[download]

Now some vmstat with sunOS:

s/de\s+sr\s+(\w\d|\w\w|\w\w\d|--|\s)+in\s+sy/de sr in sy/g
[download]

Cheers,
zlr.

If the regular expression contains ‘^TO_’ it will be substituted by ‘(^((Original-)?(Resent-)?(To |Cc |Bcc) |(X-Envelope |Apparently(-Resent)?)-To) :(.*[^-a-zA-Z0-9_.])?)’, which should catch all destination specifications containing a specific address.

If the regular expression contains ‘^TO’ it will be substituted by ‘(^((Original-)?(Resent-)?(To |Cc |Bcc) |(X-Envelope |Apparently(-Resent)?)-To) :(.*[^a-zA-Z])?)’, which should catch all destination specifications containing a specific word.

If the regular expression contains ‘^FROM_DAEMON’ it will be substituted by ‘(^(Mailing-List : |Precedence :.*(junk |bulk |list) |To : Multiple recipients of |(((Resent-)?(From |Sender) |X-Envelope-From) : |>?From )([^>]*[^(.%@a-z0-9])?(Post(ma?(st(e?r)? |n) |office) |(send)?Mail(er)? |daemon |m(mdf |ajordomo) |n?uucp |LIST(SERV |proc) |NETSERV |o(wner |ps) |r(e(quest |sponse) |oot) |b(ounce |bs\.smtp) |echo |mirror |s(erv(ices? |er) |mtp(error)? |ystem) |A(dmin(istrator)? |MMGR |utoanswer))(([^).! :a-z0-9][-_a-z0-9]*)?[%@>\t ][^<)]*(\(.*\).*)?)?$([^>] |$)))’, which should catch mails coming from most daemons (how’s that for a regular expression :-).

If the regular expression contains ‘^FROM_MAILER’ it will be substituted by ‘(^(((Resent-)?(From |Sender) |X-Envelope-From) : |>?From )([^>]*[^(.%@a-z0-9])?(Post(ma(st(er)? |n) |office) |(send)?Mail(er)? |daemon |mmdf |n?uucp |ops |r(esponse |oot) |(bbs\.)?smtp(error)? |s(erv(ices? |er) |ystem) |A(dmin(istrator)? |MMGR))(([^).! :a-z0-9][-_a-z0-9]*)?[%@>\t ][^<)]*(\(.*\).*)?)?$([^>] |$))’ (a stripped down version of ‘^FROM_DAEMON’), which should catch mails coming from most mailer-daemons.