Match details update
Most changes in T-Regx since the last Blog post were to
Match details. We
added user data (
which can be used in chained calls (e.g.
The second change is
parseInt() which allow you to handle "real" integers safetly -
without the fear of "PHP smart" integers (e.g. PHP thinks that
1000). T-Regx understands that robust applications
can't allow numbers to be
10e4 - it should be treated as an invalid integer by default!
Match.group(int|string) is now validated (T-Regx was waiting a bit for this change!). We believe that using an
invalid group name is a sign of a bug, so using
group('!@#') now throws
as it's more suitable than assuming that
-1 is just an unmatched group.