Re: Disadvantage of using 'eq' operator to compare numbers.

[holli]

Not silly.

C:\>perl -e "print 12 == 0xC"
1
C:\>perl -e "print 12 eq 0xC"
1

What the f…?

[afoken]

Looking at print 12 == 0xC and print 12 eq 0xC with the eyes of a parser, I see the following:

• Compare two values using numeric compare (first case, ==) or string-compare (second case, eq)
• LHS value is not a string (no quotes, no bareword rules apply), but a decimal number literal (12), with a value of 12 (decimal)
• RHS value is not a string (no quotes, no bareword rules apply), but a hexadecimal (0x) number literal (0xC), also with a value of 12 (decimal).
• In the first case, both values are already numbers, no need to convert. Both values are constant and equal (12). In the second case, both values have to be converted to strings. After that, both values are constant and equal ("12").
• Optimizing leaves a single true value (1).
• Call the print function with that value.

This works exactly the same with octal constants (014), and makes the code look even more confusing because of the "innocent" zero: Both print 12 == 014 and print 12 eq 014 end printing a 1.

Alexander