You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default greediness (the regex always eating its way up to the end of the entire source string, if at all possible) is not always what users want, especially when matching long structured text (like code) consisting of short atoms.
And I haven't seen "greedy" mentioned even once at the extended regex reference page, while it's readily available with ECMA's, per-pattern.
And ECMA is the JS and C++ native regex grammar anyway.
The text was updated successfully, but these errors were encountered:
xparq
changed the title
Switch regex grammar to ECMA from POSIX2, for non-greedy ops.
Switch regex grammar (from POSIX2) to ECMA (for its non-greedy ops.)
Sep 8, 2023
xparq
changed the title
Switch regex grammar (from POSIX2) to ECMA (for its non-greedy ops.)
Switch regex grammar (from POSIX2) to ECMA (for its PERL-style non-greedy ops.)
Sep 8, 2023
The default greediness (the regex always eating its way up to the end of the entire source string, if at all possible) is not always what users want, especially when matching long structured text (like code) consisting of short atoms.
And I haven't seen "greedy" mentioned even once at the extended regex reference page, while it's readily available with ECMA's, per-pattern.
And ECMA is the JS and C++ native regex grammar anyway.
The text was updated successfully, but these errors were encountered: