Then you can ignore the text stored by the “date” group and this particular difference between these flavors. If you want to extract the dates from the match, the best solution is to add another capturing group for each date. You can remember this by the fact that Perl uses ampersands for subroutine calls in procedural code too. JGsoft V2 behaves like Perl when you use the second regular expression. You can remember this by the fact that the \g syntax is a Ruby invention, later copied by PCRE. JGsoft V2 behaves like Ruby when you use the first regular expression. PCRE behaves as Perl in this case, even when you use the Ruby syntax with PCRE. Any subroutine calls to the group don’t change that. But the “Born” date was matched with a normal named capturing group which stored the text that it matched normally. In Perl, the subroutine calls did not capture anything at all. When the Perl solution matches the same, retrieving $+ will get you 1. When the Ruby solution matches the sample above, retrieving the contents of the capturing group “date” will get you which was matched by the last subroutine call to that group. In Perl, PCRE, and Boost a subroutine call does not affect the group that is called. First of all, in Ruby a subroutine call makes the capturing group store the text matched during the subroutine call. Unfortunately, there are differences in how these three regex flavors treat subroutine calls beyond their syntax. Perl needs slightly different syntax, which also works in PCRE: (?: Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec ) In Ruby or PCRE, we can use this regular expression:īorn: \ (?'date' (?: 3 | | ) This tutorial introduced regular expression subroutines with this example that we want to match accurately:
0 kommentar(er)
