In most other compiled languages, you get all errors and some number of warnings at compile time, and then you have the ability to vary the number of warnings.

As I understand things (never used it), strict causes things that wouldn't otherwise have been errors to be errors and is recommended. I think this is a bad idea. Better to have anything that is that dangerous always be an error. Ask yourself: is it an error or isn't it?

Warnings on the other hand, should have variable levels. Pick a few things that generally are bad bad errors but might be ok and use that as a starting point, then leave it up to the user to turn them all on or all off.

Can you tell I code more in C than Perl? :-)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.