in reply to Porting Perl 5.6 to Perl 5.8 issue with self-tie

If anyone has ideas on how to:
1. cause output from print and printf
2. for both STDOUT and STDERR
3. to go to successive log files within the same perl 5.8 session I would be extremely grateful.
I'm part of a team who successfully switched from a printf-to-stdout approach to using Log::Log4perl for logging all kinds of messages. Log4perl is easy to use, and very configurable. Destinations range from (automatically rotated) files, database(s) as well as stdout.

One advantage with a logging framework is that it allows you to leave (disabled) debugging statements in production code that can be enabled at will. This can make save your day when things start to fail in your deployed systems.

You may want to benchmark performance with and without logging enabled if your application is very sensitive performance-wise.

Andreas
--
  • Comment on Re: Porting Perl 5.6 to Perl 5.8 issue with self-tie

Replies are listed 'Best First'.
Re^2: Porting Perl 5.6 to Perl 5.8 issue with self-tie
by fwashbur (Sexton) on Dec 11, 2006 at 22:33 UTC
    Thanks Andreas,

    I did not know about this module, I'll have a look to see what it has to offer. The logging we are performing is not intensive, so it could fit the bill.

    Rick