Re^5: Yet Another Rosetta Code Problem (Perl, Ruby, Python, Haskell, ...) (js)

Does that imply that Javascript has different capture semantics than perl?

No. It is just that match() returns the matched substrings, not the captured substrings. If //g in a list context could be told to return the matched substrings (what it does when there are no capturing parens), then the same solution would work in Perl.

A better JavaScript solution is actually: "ZBBBCZZ".match(/(.)\1*/g). No need for the second set of parens.

- tye

Comment on Re^5: Yet Another Rosetta Code Problem (Perl, Ruby, Python, Haskell, ...) (js) Download Code

Replies are listed 'Best First'.
Re^6: Yet Another Rosetta Code Problem (Perl, Ruby, Python, Haskell, ...) (??{}) by pKai (Priest) on Sep 22, 2007 at 10:54 UTC
Telling `m//g` in list context to forget about the captures and just return the matches: `@list = "ZBBCZZ" =~ /(??{'(.)\1*'})/g;` [download] or probably more exact: there are no captures `m//` can see	[reply] [d/l] [select]