Hello rsFalse,

I suspect the warning is generated by an heuristic derived from the nature of the and operator, which interprets its operands as boolean values. Perl therefore expects the expression on the left hand side of the and to contain a boolean operator, such as ==, rather than the assignment operator. It is noteworthy that when the and is replaced by a comma, as in choroba’s preferred syntax, the warning disappears.

You are probably correct in thinking that assignment of a non-numeric value should generate a warning of the form Found = in conditional, should be eq at.... However, perldiag contains no such warning: I guess Found = in conditional, should be == is considered sufficiently indicative of the (potential) problem.

Hope that helps,