Look, sticking with ERE is like using a flip phone in the smartphone era. It's ancient. PCRE is basically the industry standard now – way more powerful and less of a headache.

Here’s why moving to PCRE is a no-brainer:

It’s way more feature-rich. We get lookaheads, lookbehinds, and non-greedy matching right out of the box. No more hacky workarounds for stuff that should be simple.

Better performance. In most real-world cases, PCRE engines are seriously optimized. It’s faster and more efficient.

Easier to read and maintain. The syntax is cleaner and more consistent. Saves dev time and reduces bugs – who doesn’t want that?

Massive community support. Pretty much every modern language supports PCRE or a close variant. Finding help or libraries is a breeze compared to ERE.

Future-proofing. ERE is basically legacy at this point. All the new tooling and regex innovations are happening in the PCRE-compatible world. Sticking with ERE is just creating tech debt for later.

The switch is low-effort and the payoff is huge. Let’s stop wrestling with an outdated tool and upgrade to what everyone else is already using.

i vote support

I vote how many times in the last 10 years you've used any Tixati function in which that would make a noticeable difference.

I hope tixati's RSS can, like BiglyBT, support filtering keywords such as 720p, 2160p, 3D, UHD, HDR, DOVI, as well as regular expressions (Ed{2}|Ed{3}|Ed{4}). BiglyBT can filter both in a single RSS feed, but tixati can only filter one of them.

Thanks for the idea.

I'll probably get this into v3.41.  Currently using std::regex on all platforms, but it shouldn't take too long to compile PCRE2 for linux/win/android and get it all linked up.

Just wrapping up 3.39 right now and I don't want to delay it any further.