Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re^2: Parsing and translating Perl Regexes

by LanX (Bishop)
on Nov 05, 2013 at 02:00 UTC ( #1061228=note: print w/replies, xml ) Need Help??

in reply to Re: Parsing and translating Perl Regexes
in thread Parsing and translating Perl Regexes

Despite the name is PCRE ... not compatible , I recommend here reading Friedl's book about Mastering Regular Expressions.

JS' RegEx is based on Perl4, so plenty of things must be excluded.

eLISP RegEx predates Perl (i.e. old POSIX), many escapes are inverted - e.g. \( <-> ( - and since regexes are always strings, any slash must be additionally escaped from string interpolation (leading to so called "slasheritis")

Hope the last 2 phrases were still readable for you.

Cheers Rolf

( addicted to the Perl Programming Language)

  • Comment on Re^2: Parsing and translating Perl Regexes

Replies are listed 'Best First'.
Re^3: Parsing and translating Perl Regexes
by wollmers (Scribe) on Nov 05, 2013 at 13:23 UTC

    What people name REGEX comes in 3 main dialects:

    • POSIX basic
    • POSIX extended
    • Perl

    The above also have dialect/implementation variants.

    And there are the different REGEX-notations used in other sciences like linguistics, which Friedl AFAIR does not include in his book.

    Helmut Wollmersdorfer

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1061228]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (3)
As of 2018-01-18 22:29 GMT
Find Nodes?
    Voting Booth?
    How did you see in the new year?

    Results (215 votes). Check out past polls.