[OT] Perl woes

[Piers Cawley]

On Wed, Jan 28, 2009 at 10:56 AM, Jonathan Kimmitt
<Jonathan.Kimmitt at csr.com> wrote:
>        Whoever said, the primary purpose of a compiler is to check for
> errors,
>        and only if there are no errors, create the code, was most
> definitely not talking about Perl.
>
>        The next time I use == instead of eq to compare two strings, I
> will know to expect it will always
>        evaluate to true. What other language does this (apart from C,
> which would invariably return false)

If only it were that simple:

'10' == 'something' # false

>        It would be a trivial matter to return an error or warning if ==
> is used for items which aren't numbers

Actually, I was surprised to find that there isn't a warning for that
with warnings turned on. Memory proving faulty.