Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

If it helps at all, I develop software that runs on embedded systems like printers and factory robots. We develop in C, rather than Perl, but we not only have all build-time warnings turned up to maximum, but we won't accept any production code in which any warning occurs, for the same reasons as are mentioned above. We leave those on at all times, although the ASSERT macro does get commented out for release systems, but only because some of the tests take appreciable amounts of time.

For our systems as well as for Perl, having a log of user activity -- especially of any warnings generated -- is essential when bugs or problems occur. It's almost impossible to fix a bug if you can't reproduce it, and a good set of warning messages will let you do so. You may also want to dump your errors or warnings to a file rather than to the display, if a 'flawless' look is required for the user interface. On newer systems, we sometimes make the log file a rotating log -- it only retains the last 10 minutes' warnings (or whatever), but that's just to make it easier to manage a large volume of data. You shouldn't need that feature in a working system.


In reply to Re: Warnings and Strict in Production/Performance by Dervish
in thread Warnings and Strict in Production/Performance by deep submerge

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.