Re: Module implementing modified comment-style debugging.

Smart::Comments might meet your needs as stated more closely, but have a look at Log::Log4perl, it's very nice. Among other things, you can change logging level for individual parts of you system, without having to restart the system.

Comment on Re: Module implementing modified comment-style debugging.

Replies are listed 'Best First'.
Re^2: Module implementing modified comment-style debugging. by andreas1234567 (Vicar) on May 01, 2008 at 05:58 UTC
I'd also go for Log::Log4perl. As you can see, leaving log statements in production code with logging disabled makes close to no impact on overall performance (it's actually faster in this benchmark :). Using the `init_and_watch` option, you can tune the log levels while the program is running (as noted by stiller). That is a property I value very much when arriving at a customer site and the system's symptoms are hard to interpret. Simply increase the log level for individual parts of the system, and see how it actually runs. Read more... (2 kB) `$ /usr/bin/perl l4p_bench.pl Rate fib_no_log fib_log_1 fib_no_log 997050/s -- -3% fib_log_1 1025993/s 3% --` [download] -- No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Module implementing modified comment-style debugging.
by andreas1234567 (Vicar) on May 01, 2008 at 05:58 UTC

Log::Log4perl

no impact on overall performance

faster

init_and_watch

stiller

Read more... (2 kB)

$ /usr/bin/perl l4p_bench.pl
                Rate fib_no_log  fib_log_1
fib_no_log  997050/s         --        -3%
fib_log_1  1025993/s         3%         --
[download]

--
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]

[reply]
[d/l]
[select]