FYI:It is perfectly legal to have a space between a variable and the ++ operator:

my $count_variable = 0;
$count_variable ++;
$count_variable
++;
print $count_variable; # prints: 2
[download]

$s = 0;
print $s ++ for 1..9;
[download]

Will not increment. Apparently, it depends on the context, whether the whitespace matters.

mkmcconn

update: danger, I'm sure you must be right about the prototyping of print().

There have to be exceptions to every rule :-). This was obviously not the problem with the present question though. And, I am inclined think this is perhaps a little bug:

sub blah {
    print shift;
}
blah($s ++) for 1 .. 9;   # works fine
blah $s ++  for 1 .. 9;   # syntax error

print $s ++  for 1 .. 9;   # syntax error
print($s ++) for 1 .. 9;   # syntax error
[download]

The latter print() case is probably related to print()'s prototype for optionally accepting a filehandle).

My first reaction was also that the space is wrong, but then tye corrected me in the CB so I did a bit of experimenting and found surprising (to me) results. Guess what this snippet will do:

print $foo;
print $foo ++;
print $foo, $foo ++;
[download]

--
I'd like to be able to assign to an luser

The second line is one of the strange cases with whitespace. This is due to the "indirect object" syntax where the first argument can be missing the separating comma to indicate that it is a file handle (in the case of print). Like I said, there are some interesting exceptions but for most things spacing doesn't matter.

        - tye (but my friends call me "Tye")