in reply to Re: warnings and strict -- The 2 Best Ways You Can Improve Your Programming
in thread warnings and strict -- The 2 Best Ways You Can Improve Your Programming

The only things they do help with are generally the problems that are easiest to fix anyway.
Agreed.  But those problems that are "easiest to fix" become so only after you've reached a certain state of enlightment with Perl.  My point is that you start out miles ahead by using these tools, and they give you invaluable habits which stick with you.  Furthermore, all of the very good bullet items you list are, in my opinion, things that you develop along the path to programming (be it Perl or any language).  I think we can both agree that nobody has a panacea for obtaining them in a short time.

It's also true that the tools warnings and strict are most necessary for the beginning Perl programmer.  But, having said that, I'm not going to give them up anytime soon.  (:

  • Comment on Re^2: warnings and strict -- The 2 Best Ways You Can Improve Your Programming

Replies are listed 'Best First'.
Re^3: warnings and strict -- The 2 Best Ways You Can Improve Your Programming
by Perl Mouse (Chaplain) on Oct 05, 2005 at 08:49 UTC
    Miles ahead? I think you have a long way to go if you think that just adding "use strict" and "use warnings" gives you such a headstart.

    I always use warnings and strict (and know when to turn it off), but I've always considered them to be in the same class as the lights on my dashboard to remind me that the handbrakes are on, or that my oil level is low. Useful, but they don't make me a better driver. And they don't prevent accidents either.

    Perl --((8:>*