https://bugs.exim.org/show_bug.cgi?id=2120
--- Comment #10 from Rob <r...@playjax.net> ---
I think the issue isnt "Javascript compatibility" so much as "strict versus
permissive". Javascript is historically permissive, whereas PCRE seems strict
by design. So if you add another option, "permissive" might be a better concept
for it.
In any case, I dont think i have any choice but to continue hacking my way
through new incompatibilities as i discover through random website testing. For
example, on the Scientific American website, pcre2_compile returns an error for
the the following regex ...
var c = /(android|webos|palm\os|qnx|bada|rim\stablet\sos|meego|contiki)/;
The \o would be interpreted as a literal 'o' in Javascript but PCRE expects
\o{argument} and returns an error. It wouldnt be worth wasting a second option
on that unless you combined the two issues into one "permissive" option.
I'll keep testing and hacking, and once i've got a more complete list of
Javascript incompatibilities i'll send them through.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
