Editing Talk:1171: Perl Problems

The punchline is in reference to this oft-quoted joke by jwz:

Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems. - Jamie Zawinski

There's actually a double joke here: The song "99 Problems" is by Jay-Z, and the regex joke is by jwz.
--[[Special:Contributions/173.8.183.86|173.8.183.86]] 08:33, 8 February 2013 (UTC)
:[Jj][A-Za-z]*[\b\-]*[Zz][A-Za-z]* [[User:Elsbree|Elsbree]] ([[User talk:Elsbree|talk]]) 17:31, 8 February 2013 (UTC)

I don't understand why so many people have problems with regular expressions. They are really easy ... compared to gramatics or turing machines. :-)
(Of course, it is good idea to verify that the problem you are trying to solve with regular expressions IS regular. While perl is sometimes capable of doing stuff outside real regular expressions, it's rarely worth it.) -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 10:23, 8 February 2013 (UTC)

Wait, how do we rule out that the Regular Expressions might've helped Cueball, and that now, in fact, he has only 4 problems? [[Special:Contributions/220.224.246.97|220.224.246.97]] 15:52, 8 February 2013 (UTC)

Great explanation today, folks. --[[User:DanB|DanB]] ([[User talk:DanB|talk]]) 20:10, 8 February 2013 (UTC)

The stuff about preg_match is NOT '''perl''' at all.  It is '''php'''. 
'''perl''' has regular expression matching as part of the language, not as a function.
In perl, you would normally only get the firrst match, unless you used the 'g' flag.
The comparable initial match might be:  <code>@matches = $str =~ m/([A-Za-z])/g;</code>
But if you only wanted the first match, it would be more common to write something like <code>$firstMatch = $str =~ m/([A-Za-z])/ && $1;</code>
I think that if you do want all the matches in perl, you are better off doing it in an explicit loop, so as to avoid creating an unneeded array.
(Perl now considers using the "complete match" token to be a less than ideal thing to use, which is why I added the parens and used <code>$1</code> instead of <code>$&</code>.)  --[[User:Divad27182|Divad27182]] ([[User talk:Divad27182|talk]]) 06:33, 9 February 2013 (UTC)

If you're havin' Perl problems I feel bad for you, son - I got 99 problems, but regex ain't one. {{unsigned|‎150.252.114.126}}

[User talk:Divad27182] is right. I took the liberty to remove the Perl reference in that line. [[Special:Contributions/87.165.125.229|87.165.125.229]] 10:05, 11 February 2013 (UTC)

[[Special:Contributions/192.193.116.137|192.193.116.137]] 15:47, 11 February 2013 (UTC)Is there not an "off by one" joke in here also?
@@ Line 21: / Line 21: @@
 I think that if you do want all the matches in perl, you are better off doing it in an explicit loop, so as to avoid creating an unneeded array.
 (Perl now considers using the "complete match" token to be a less than ideal thing to use, which is why I added the parens and used <code>$1</code> instead of <code>$&</code>.)  --[[User:Divad27182|Divad27182]] ([[User talk:Divad27182|talk]]) 06:33, 9 February 2013 (UTC)
-:<code>($firstMatch) = $str =~ /([a-z])/i</code> [[Special:Contributions/199.27.128.24|199.27.128.24]] 05:36, 13 January 2014 (UTC)
 If you're havin' Perl problems I feel bad for you, son - I got 99 problems, but regex ain't one. {{unsigned|‎150.252.114.126}}
@@ Line 29: / Line 27: @@
 [[Special:Contributions/192.193.116.137|192.193.116.137]] 15:47, 11 February 2013 (UTC)Is there not an "off by one" joke in here also?
-::"I don't understand why so many people have problems with regular expressions." I think there are a few reasons
-::1: the syntax crams everything together giving the coder little scope for laying things out. As the number of levels of nesting increases this makes it very hard to see the tree structure.
-::2: the way syntax characters are mixed with literal characters without clear delimination makes it very difficult for those who are not intimately famility with the format to quickly distinguish which is syntax and what is literal text to be matched (see shell script for an example of a programming language that has the same problem) or to curse when they don't realise a paticular character is used as syntax.
-::3: there is little in the way of debugging support when a regex doesn't match the way you expect it to.
-::4: there are some really nasty corner cases of regexes that are simple to write but massively hard for the regex engine to check [http://www.regular-expressions.info/catastrophic.html]. -- [[w:user:plugwash]] {{unsigned ip|141.101.98.248}}
-Very late to the party but I wanted to reply to [[w:user:plugwash]]  and say that Perl has at least made an improvement on your point 1. "the syntax crams everything together giving the coder little scope for laying things out". One can use the x flag, which allows arbitrary amounts of whitespace in the regex:
-<code>
-    $str = 'foobar';
-    $result = $str =~ m/
-        foo
-        (
-            [b|c]
-        )
-        [^z]
-        r
-    /x;
-    print "Result: $result\n";
-    print "Captured: $1\n";
-</code>
-With of course the remaining problem being if you ''want'' whitespace, you have to explicitly add it back in.  [[User:AmbroseChapel|AmbroseChapel]] ([[User talk:AmbroseChapel|talk]]) 06:24, 31 August 2017 (UTC)
-If I can take a second to point this out for you youngsters, the "I got 99 problems but a bitch ain't one" line came from Ice T originally (from "99 Problems" on the "Home Invasion" album: hardly his best work. [[Special:Contributions/141.101.107.84|141.101.107.84]] 15:16, 20 September 2017 (UTC)Endie