Re: Parsing and translating Perl Regexes

This node falls below the community's threshold of quality. You may see it by logging in.

Comment on Re: Parsing and translating Perl Regexes

Replies are listed 'Best First'.
Re^2: Parsing and translating Perl Regexes by LanX (Saint) on Nov 05, 2013 at 02:00 UTC
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)	[reply]
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	[reply]
Re^2: Parsing and translating Perl Regexes by Anonymous Monk on Nov 05, 2013 at 01:48 UTC
... what exactly is The Problem Here? ... Too many italics	[reply]