Re: Confusing grep behavior

You need to reread grep

my @res = grep $_ split(",", "a,b,c,d,,f,,h"); #is a syntax error.
[download]

According to the POD when grep is not called with a block it requires a comma before the list you are working on.
grep EXPR,LIST

So this will work as you expect.

my @res = grep $_, split(",", "a,b,c,d,,f,,h");
[download]

grep
One dead unjugged rabbit fish later...

Comment on Re: Confusing grep behavior Select or Download Code

Replies are listed 'Best First'.
Re^2: Confusing grep behavior by dextius (Monk) on Dec 04, 2007 at 23:33 UTC
You are quite right.. I should rephrase my question... On Mac OS X, the comma isn't required, and has far different behavior. Anyone happen to know what that is?	[reply]
Re^3: Confusing grep behavior by perrin (Chancellor) on Dec 04, 2007 at 23:52 UTC
It's not a Mac thing. 5.8.5 on Linux allows it as well. I'm guessing it's a bug that was fixed in 5.8.7 or 5.8.8.	[reply]
Re^4: Confusing grep behavior by dextius (Monk) on Dec 05, 2007 at 00:44 UTC
Thanks, I wasn't aware of the bug, and was just confused since I wasn't getting a syntax error.	[reply]
Re^3: Confusing grep behavior by grep (Monsignor) on Dec 05, 2007 at 00:44 UTC
No matter what OS you run it on the comma is still required, as noted by the POD and (quite noticeably) by the incorrect performance. The only difference(bug) is that it didn't throw an error. A crime is still a crime, whether you get caught or not :). grep `One dead unjugged rabbit fish later...`	[reply]