in reply to problem with print content of file

In the interest of feedback:

I voted you down because you didn't use "warnings" or "strict".

You have been here for half a month and you haven't picked this up, yet.

While "warnings" and "strict" are not necessary, they are good common practice by a perl programmer. They make bug fixing easier, and they save time.

Look at Some things that will make your life easier as a Perl coder.

J. J. Horner
Linux, Perl, Apache, Stronghold, Unix
  • Comment on (jjhorner)problem with print content of file

Replies are listed 'Best First'.
(Ovid - don't always need -w and strict) RE: problem with print content of file
by Ovid (Cardinal) on Aug 07, 2000 at 21:40 UTC
    While I agree with your general idea of voting down experienced monks who don't use -w or strict, I can't say that it's always appropriate.

    For example, this post doesn't even have a shebang line. That suggests to me that this is a code snippet and not the entire program. Hence, no -w or strict. Also, sometimes we're just writing a quick throwaway that won't be reused. While I tend to use -w and strict even for my throwaways (because I've been known to shoot myself in the foot), I wouldn't argue that you always need to be that careful on a one-shot deal.

    Despite the above comments, I do accept the general rule about using -w and strict and have voted monks down for that in the past.

    And kudos to you for telling this monk why you voted --.