-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port to EREs #24
Comments
Plus, the escaping is a nightmare anyway. |
strugee
added a commit
that referenced
this issue
Oct 14, 2018
Closes #24. Note that this is required for POSIX compatibility since \| in BREs is apparently a GNU extension. See https://stackoverflow.com/a/22877494/1198896#comment34926946_22877494, along with POSIX.1-2017 (IEEE Std 1003.1-2017), Section 9.3: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html
strugee
added a commit
that referenced
this issue
Oct 15, 2018
Closes #24. Note that this is required for POSIX compatibility since \| in BREs is apparently a GNU extension. See https://stackoverflow.com/a/22877494/1198896#comment34926946_22877494, along with POSIX.1-2017 (IEEE Std 1003.1-2017), Section 9.3: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html
strugee
added a commit
that referenced
this issue
Oct 15, 2018
Closes #24. Note that this is required for POSIX compatibility since \| in BREs is apparently a GNU extension. See https://stackoverflow.com/a/22877494/1198896#comment34926946_22877494, along with POSIX.1-2017 (IEEE Std 1003.1-2017), Section 9.3: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html Plus, I'm pretty sure we'll get a performance boost since EREs don't have capturing groups.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can't use
|
in BREs portably, which is a no-go. See https://stackoverflow.com/questions/22877457/can-a-b-expression-be-used-in-grep-bre-mode#comment34926946_22877494.The solution is to port to EREs which will let us use
|
portably.The text was updated successfully, but these errors were encountered: