Re: In Defense of Smart::Comments

Smart::Comments does have a shortcoming which I find serious. This is, it prints all its output to the screen via STDERR. This is hardwired; there's no way to change it, except perhaps by redirecting STDERR elsewhere.

This is just one on many reasons to use Log::Log4perl instead of Smart::Comments. I often use it together with Log::Dispatch::FileRotate to retain a given number of logs of a known size to be able to backtrack problems after the fact.

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

Comment on Re: In Defense of Smart::Comments

Replies are listed 'Best First'.
Re^2: In Defense of Smart::Comments by rbothe (Initiate) on Jun 16, 2011 at 08:27 UTC
just a remark I like smart comments But from the past i documented my scripts (sh,perl,c,...) with many lines of form: ### @(#)description of prog, author, dependencies, ... Obviously there could arise problems if we use this style together with smart comments NB the '### @(#)' style documentation goes back to the (not more used?) "what" programm, part of the (not more used?) "documenters work bench" :-) Simple solution is "use Smart::Comments '####';"	[reply]

Replies are listed 'Best First'.

Re^2: In Defense of Smart::Comments
by rbothe (Initiate) on Jun 16, 2011 at 08:27 UTC

just a remark I like smart comments But from the past i documented my scripts (sh,perl,c,...) with many lines of form: ### @(#)description of prog, author, dependencies, ... Obviously there could arise problems if we use this style together with smart comments NB the '### @(#)' style documentation goes back to the (not more used?) "what" programm, part of the (not more used?) "documenters work bench" :-) Simple solution is "use Smart::Comments '####';"

[reply]