Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: (jeffa) 3Re: Things every perl programmer should know?

by barbie (Deacon)
on Jun 06, 2003 at 12:10 UTC ( #263644=note: print w/replies, xml ) Need Help??

in reply to (jeffa) 3Re: Things every perl programmer should know?
in thread Things every perl programmer should know?

Teach 'em the rules now, let 'em break the rules after the learn them

That was my point on particular mailing list. There are far too many new programmers, not just in Perl, that have never been taught good programming. In Perl scripts using warnings and strict helps you in learning some good Perl programming practices.

When writing C programs, I always used 'lint' before compiling and to me warnings and strict are the equivalent. It has taken time, but most Perl programmers I've worked with have gotten used to adding -w/use strict without thinking. In a company I used to work for, they had to port a badly written application to mod_perl. It took several months. The app that I was working on took a couple of weeks to be mod_perl compliant. They have since seen the light :)

Another thing every Perl programmer should be taught is Testing. Its amazing how often the Test:: modules can keep you sane, when all else is driving you nuts with fustration.

Birmingham Perl Mongers
Web Site:

  • Comment on Re: (jeffa) 3Re: Things every perl programmer should know?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://263644]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (9)
As of 2018-05-23 15:52 GMT
Find Nodes?
    Voting Booth?