http://qs321.pair.com?node_id=1009495


in reply to Re^3: 'Dynamic scoping' of capture variables ($1, $2, etc.)
in thread 'Dynamic scoping' of capture variables ($1, $2, etc.)

Thanks for your explanation Moritz. I meant $1 value got changed similar to $_ value for better understanding. I know that $_ value getting changed due to substitute operator replaces matched digits to null string. I have a doubt in your example, how $1 value getting changed every recursive call. As per your code, your m// expression will match first digits ( 55 ) at all time as per my understanding. Of course, when I checked the code, it gives $1 value as 55, 666, 7777 and 1 respectively. Kindly give me some detail about it.
  • Comment on Re^4: 'Dynamic scoping' of capture variables ($1, $2, etc.)

Replies are listed 'Best First'.
Re^5: 'Dynamic scoping' of capture variables ($1, $2, etc.)
by moritz (Cardinal) on Dec 19, 2012 at 06:21 UTC
    As per your code, your m// expression will match first digits ( 55 ) at all time as per my understanding

    No, because I used m/../g in scalar context, which remembers the previous match position in pos, and then always returns the next match during subsequent calls.

    Maybe you are more familiar with it in this idiom:

    use 5.010; $_ = 'a123b45c6'; while (m/(\d+)/g) { say $1; }
      Thanks for your explanation. I got it.