Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "pcre"
-
Ugh! Anyone also finds it incredibly annoying that regex notations can change between programs? And I don't mean like PCRE vs jS, those are functional differences.
I mean like... In sed, I always spend trying out all possible combos of backspacing when dealing with special notations like quantifiers {}, sets [], match groups () and so on!
Why can't it be just so that backslash anything = character literal, and not the functional counterpart.
Or at least stick to either one of the options, not like sed, where matchgroup is \(\), quantifier \{\} but a set is just []
Also wish sed supported reluctant quantifier (*?), having to use negative character set matching makes it much less readable...3 -
Arghhhhh working with regular expressions (already a bad start) got it working on my dev PC but it won't work on the server.
The only difference is my pc is running PCRE v8.41 and my server is running v8.42. Can't find anyone else having the same issue on SO/Google8