I don't understand the effort to use split and map in solutions. Even with this latest version of the assumed implied requirement, a good, old s/// seems the best way:
c:\@Work\Perl\monks>perl -wMstrict -le
"my $word = '$-.%aBc&/d-E';
;;
(my $new_word = $word) =~ s{ ([^[:alpha:]]+ | [[:alpha:]]) }{[$1]}xms
+g;
;;
print qq{'$word' -> '$new_word'};
"
'$-.%aBc&/d-E' -> '[$-.%][a][B][c][&/][d][-][E]'
Give a man a fish: <%-{-{-{-<
| [reply] [d/l] [select] |
In the end it comes down to readability, and readability depends on the comprehension level of the reader.
You have a much higher level of regex-fu than I do, so yours is clear and understandable. I just had to look at it carefully before I could clearly see what it was doing.
PS Good job -- that's a very nice piece of code.
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
| [reply] |
I don't understand the effort to use split and map in solutions.
As the one who first introduced them, I wasn't making any special effort to use split or map. As I (mis)understood the spec, it was the most natural approach to a solution. At a human-level description, if you have a string and want to put brackets around each character, do you search the string for characters and, each time you find one, change it to a three-character sequence of the same character preceded and followed by brackets ($word =~ s/./[$1]/g); or do you consider the text as a list of characters (split '', $word) and put brackets around each of them (map { "[$_]" }, @chars)? Personally, if I were doing it by hand, I'd take the latter approach, and I expect pretty much anyone else would, too.
But, as already pointed out, I misunderstood the spec as wanting to bracket all characters, not only letters. With that limitation in place, the "treat it as a list of characters, not searching in a string" approach still works with a minor modification, and much more simply than the earlier attempts to fix it:
$new_word = join "", map { $_ =~ /[a-zA-Z]/ ? "[$_]" : $_ } split "",
+$word;
Again following the "how would I do it by hand?" approach, this changes the map from "put brackets around each character" to "put brackets around characters in a-zA-Z and leave any other characters as-is", thus transforming "layer123" to "[l][a][y][e][r]123". | [reply] [d/l] [select] |
c:\@Work\Perl\monks>perl -wMstrict -le
"for my $word (qw(XYZ$-.%abc&/ $-.%abc&/XYZ $-.%abc&/XYZ+=*)) {
my @group1 = ( $word =~
m/(?:
([^a-zA-Z]+)
([a-zA-Z]+)
)+
([^a-zA-Z]+)
/x );
my @group2 =
map { $_ =~ /[a-zA-Z]/ ? split( //, $_ ) : $_ } @group1;
my $new_word = join ( '', map { qq{[$_]} } @group2 );
print qq{'$word' -> '$new_word'};
}
"
'XYZ$-.%abc&/' -> '[$-.%][a][b][c][&/]'
'$-.%abc&/XYZ' -> '[$-.%][a][b][c][&/]'
'$-.%abc&/XYZ+=*' -> '[&/][X][Y][Z][+=*]'
(Again, this assumes that we can, to begin with, even arrive at a common understanding of what is required. :)
Give a man a fish: <%-{-{-{-<
| [reply] [d/l] [select] |
Yup -- I agree 100%. As I was writing the regex, I thought, hmm, this would break if (your example above) .. then I stopped going down that road, and just finished my post. [1]
As often happens, we were dealing with an incompletely specified problem. But even the discussion around the possible solutions is a worthwhile endeavour. :)
- "Just #$%@ing Do It." --petdance|alester, undated quotation
Alex / talexb / Toronto
Thanks PJ. We owe you so much. Groklaw -- RIP -- 2003 to 2013.
| [reply] [d/l] |