in reply to Barewords equal zero?

Running the code in a particular IDE didn't give a warning

It might therefore be a good idea to avoid that IDE.

Cheers,
Rob

Replies are listed 'Best First'.
Re^2: Barewords equal zero?
by stiller (Friar) on Feb 12, 2008 at 07:23 UTC
    Or rather use strict; to catch this errror, even when in an IDE. I doubt any IDE implements it's own Perl, so it will have to rely on ouput from the underlying Perl installation, which in turn relies on you to tell it what to do.
Re^2: Barewords equal zero?
by DrHyde (Prior) on Feb 12, 2008 at 11:03 UTC
    It would be a better idea to avoid IDEs altogether when teaching newbies. Even *Notepad* is sufficient for noddy programs like this, and you can guarantee that it won't hide any essential information - such as warnings.

      That's very macho and all, but the reductio ad absurdum is to issue the students magnetized needles, or perhaps to hold class in a butterfly farm. IMHO, a good IDE with syntax coloring is immensely helpful at catching errors early. In fact, it helps me when I'm typing without having to wait until compile time (as with strictures). Without any empirical proof I'd conjecture that when teaching newbies it has instructive value even "for noddy programs like this".


      #my sig used to say 'I humbly seek wisdom. '. Now it says:
      use strict;
      use warnings;
      I humbly seek wisdom.