Re: To DEBUG, or to COMMENT. _That

I had some exposure to this recently. One of my colleagues was quite taken with it and has started to use it quite a bit, controlling it with a command line option.

But another colleague, in the same shop, isn't fond of it inlining new code. There is also some thought that the loop comments don't play nice in a forked environment.

Overall, I think it might be useful, especially for routine debugging messages, but I'm not sure I would want to use the loop reporting very often.

The answer to the question "Can we do this?" is always an emphatic "Yes!" Just give me enough time and money.

Comment on Re: To DEBUG, or to COMMENT. _That_ is the question

Replies are listed 'Best First'.
Re^2: To DEBUG, or to COMMENT. _That_ is the question by taint (Chaplain) on Nov 08, 2013 at 21:36 UTC
Greetings, boftx. As to the inlining new code, and loops; I can easily see where that'd be undesirable. I was mostly thinking in terms of "ferreting out" issues, and simply "tracing" the code/program/script. But then using perltidy to remove the extraneous comments, and such. Then unusing `Smart::Comments` before release. :) Best wishes --Chris #!/usr/bin/perl -Tw use Perl::Always or die; my $perl_version = (5.12.5); print $perl_version;	[reply]

Replies are listed 'Best First'.

Re^2: To DEBUG, or to COMMENT. _That_ is the question
by taint (Chaplain) on Nov 08, 2013 at 21:36 UTC

As to the inlining new code, and loops; I can easily see where that'd be undesirable. I was mostly thinking in terms of "ferreting out" issues, and simply "tracing" the code/program/script.
But then using perltidy to remove the extraneous comments, and such. Then unusing Smart::Comments before release. :)

Best wishes

--Chris

#!/usr/bin/perl -Tw
use Perl::Always or die;
my $perl_version = (5.12.5);
print $perl_version;

[reply]