The problem is that you used the following grep:

grep((0 + $_) >= 99999999)
[download]

You meant to use the following grep:

grep(((0 + $_) >= 99999999), @times)
[download]

Be careful when you omit parens around arguments.

You must have had different code on your linux system. Side-effects aside,

if (EXPR, @times) { ... }
[download]

if (@times) { ... }
[download]

Note that

grep(EXPR)
[download]

grep(EXPR, @empty)
[download]

The mentions of a syntax error by the other posters is not relevant to the question; they're simply using an older version of Perl than the versions present on each of your systems.

Apparently, the Perl on the Linux PCs is even older. I won't be able to check until sometime tomorrow because they are busy running robots.

Anyway, adding parens around the arguments fixed it.

Thanks

$ perl -e '
use warnings;
use strict;

my @times = ( 1, 2, 3, 4);

print STDERR "Times: @times\n";
if (grep 0 + $_ >= 99999999, @times) { die("Time values must be < 9999
+9999"); }
'
Times: 1 2 3 4

$ perl -e '
use warnings;
use strict;

my @times = ( 1, 2, 3, 4);

print STDERR "Times: @times\n";
if (grep $_ + 0 >= 99999999, @times) { die("Time values must be < 9999
+9999"); }
'
Times: 1 2 3 4

$ perl -e '
use warnings;
use strict;

my @times = ( 1, 2, 3, 999999999999);

print STDERR "Times: @times\n";
if (grep $_ + 0 >= 99999999, @times) { die("Time values must be < 9999
+9999"); }
'
Times: 1 2 3 999999999999
Time values must be < 99999999 at -e line 8.
[download]

perl ptest.pl
Not enough arguments for grep at ptest.pl line 9, near "99999999)"
Execution of ptest.pl aborted due to compilation errors.



perl -v

This is perl 5, version 12, subversion 2 (v5.12.2) built for x86_64-li
+nux
[download]

Tip #6 from the Basic debugging checklist: B::Deparse

perl -MO=Deparse ptest.pl
Not enough arguments for grep at ptest.pl line 9, near "99999999)"
ptest.pl had compilation errors.
use warnings;
use strict 'refs';
my(@times) = (1, 2, 3, 4);
print STDERR "Times: @times\n";
if (grep, @times) {
    die 'Time values must be < 99999999';
}
[download]

the deparse on Windows is:

if (grep((0 + $_ >= 99999999)), @times)

Which looks like the expression parser is stricter than the one in the Perl on the Linux PC.

In a factory right now, and the Linux PCs are currently busy running robots, so I can't check until the next change over, sometime tomorrow. (Also can't access my office PCs until I get back to the office)

My 5.18.2 on Linux dies the same way. B::Deparse shows this interpretation of your if statement:

if (grep((0 + $_ >= 99999999)), @times) {
[download]

Adding the parentheses properly works:

if (grep (((0 + $_) >= 99999999), @times)) { ...

# prints: Times: 1 2 3 4
[download]

Also fails on Linux as listed previously; here perl is v5.16.3. What is your perl version on Linux?

5.18.0 or higher. That's when

grep(EXPR)
[download]

become a valid equivalent to

grep(EXPR, @empty)
[download]

Since you mention it, could you also summarize why? Seems a bad idea to me. I mean, we have a case right here where it would have caught a mistake. What is the point of allowing people to write useless constructs, especially when it is easy to write them by accident?

- tye