Jay Savage wrote:
As for simply redirecting STDERR, most people don't really want to do this with a daemon. If you're using strictures and warnings, you expect many daemons to produce hundres, possibly thousands, of lines of warnings, depending on the purpose of the daemon, how busy it is, and how long-lived it is. Do you really want to log every "use of undefined value" in match and/or string concatentation error? I know I don't. Nor do I want to check everything I use for definedness. If it's there, print it. If it's not, print the rest of the line, or let the match fail, or whatever.
Yes, as a matter of fact, I do. I guess it's all in how you were brought up. Having worked under contacts that state, "When compiling, warnings levels must be turned to maximum and the compile must proceed without any warnings," does give me the tendency to eliminate all warnings in my work; even those I'm not obligated to do so. However, to get rid of them:
no strict; no warnings; See `perldoc strict` and `perldoc warnings` for details. -- Just my 0.00000002 million dollars worth, --- Shawn "For the things we have to learn before we can do them, we learn by doing them." Aristotle "The man who sets out to carry a cat by its tail learns something that will always be useful and which will never grow dim or doubtful." Mark Twain "Believe in the Divine, but paddle away from the rocks." Hindu Proverb * Perl tutorials at http://perlmonks.org/?node=Tutorials * A searchable perldoc is at http://perldoc.perl.org/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
