There are different types of warnings: Perl-warnings and other warnings. I think you should never see Perl-warnings in production for multiple reasons:

• variables used without initialisation or declaration, accessing non-existent array cells; this will undoubtedly cause unreliable output
• security concerns: warnings might reveal more than you want in case security is an issue

Of course, there are other, non-Perl errors, like "Disk is almost full". These messages should be logged to a file and regularly inspected. I would not use "warn" for this.

Back to your question: I use strict in production, and depending on the type of application and its audience (general audience: no, expert audience: yes) warnings.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.