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
If you read the linked to POSIX standard, however, it seems that such empty expressions are not actually valid regexs. For example, the defined extended regex grammar is
from which I don't see how you can form () as it must contain a extended_reg_exp which has to consist of at least one ERE_branch which must consist of at least one ERE_expression which must have at least one character of some sort.
The text was updated successfully, but these errors were encountered:
I suppose this is a issue with the Wiki rather than with regex-tdfa, but there is no bug tracker at the Wiki. The Wiki does not seem to be actively maintained. It could make sense to move relevant parts of the Wiki into the documentation of one of the regex-* packages, but then it would likely be regex-base.
Feel free to close this if you want. As you said, there obviously nothing that needs to be done to the code itself. Had just happened to notice that and figured I should probably point it out. I've now added it to the talk page for the wiki entry.
Just a quick note that a lot of the other-implementations-are-not-compliant examples appear to be about empty patterns (e.g., issues with the matching of
()
in(()|.)(b)
).If you read the linked to POSIX standard, however, it seems that such empty expressions are not actually valid regexs. For example, the defined extended regex grammar is
from which I don't see how you can form
()
as it must contain aextended_reg_exp
which has to consist of at least oneERE_branch
which must consist of at least oneERE_expression
which must have at least one character of some sort.The text was updated successfully, but these errors were encountered: