m{} within grep{} causing problems? (code)

deprecated has asked for the wisdom of the Perl Monks concerning the following question:

die "malformed index file!" unless
  scalar ( grep { $_ =~ m[\d{3}-\d{3}] }, values %batch_ids ) == 6;
[download]

is returning this error:

syntax error at readmagazine.pl line 21, near "},"
[download]

where line 21 is the grep. Any ideas what the problem is? My suspicion is that the \d{3} is conflicting with grep's {}. Other than that, the syntax seems to be correctly formed to me...

thanks
brother dep.

--
Laziness, Impatience, Hubris, and Generosity.

Comment on m{} within grep{} causing problems? (code) Select or Download Code

Replies are listed 'Best First'.
Re: m{} within grep{} causing problems? by japhy (Canon) on Jun 25, 2001 at 19:43 UTC
The `grep BLOCK LIST` form takes no comma after the block -- you have a comma there. You could use the expression syntax: <code> die "..." unless grep(/\d{3}-\d{3}/, values %hash) == 6; `japhy` -- Perl and Regex Hacker	[reply]
Re: m{} within grep{} causing problems? by mikfire (Deacon) on Jun 25, 2001 at 19:48 UTC
You are confusing perl. According to perldoc -f grep, you have two choices: `grep BLOCK LIST grep EXPR,LIST` [download] Your usage is a hybrid of the two, as the curly braces indicate the beginning of a block. Both of these two forms work `scalar( grep m[\d{3}-\d{3}], values %batch_ids ) == 6;` [download] or `scalar( grep { m[\d{3}-\d{3}] } values %batch_ids ) == 6;` [download] mikfire	[reply] [d/l] [select]
Re: m{} within grep{} causing problems? by btrott (Parson) on Jun 25, 2001 at 19:44 UTC
Your problem is that the grep form that you're using, grep BLOCK LIST, does not use a comma (',') after the BLOCK. Take out the comma and it will compile.	[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks