The question is should we allow space within the braces of things like
\b{} {m,n} quantifiers, etc, regardless of the /x modifier setting?
Space is already allowed within Unicode property definitions
\p{ foo = bar }
is perfectly legal without /x. This was because the Unicode standard
required it. The space is only valid adjacent to the braces and the
equals sign.
I believe this is the only case where it is legal, however. You can't
say \x{ df } or \b{ wb }, for example, even under /x.
It has long been planned to bring Perl to parity with other languages so
as to be able to omit the lower bound in a curly quantifier, a{,3} would
have a lower bound of 0. We are now in a position to do that. We could
choose to allow white space within this construct 1) never; 2) always;
3) with /x.
I don't really know what is the right decision.
\b{} {m,n} quantifiers, etc, regardless of the /x modifier setting?
Space is already allowed within Unicode property definitions
\p{ foo = bar }
is perfectly legal without /x. This was because the Unicode standard
required it. The space is only valid adjacent to the braces and the
equals sign.
I believe this is the only case where it is legal, however. You can't
say \x{ df } or \b{ wb }, for example, even under /x.
It has long been planned to bring Perl to parity with other languages so
as to be able to omit the lower bound in a curly quantifier, a{,3} would
have a lower bound of 0. We are now in a position to do that. We could
choose to allow white space within this construct 1) never; 2) always;
3) with /x.
I don't really know what is the right decision.