comment on

> A good idea, I was hoping for something even cleaner, that won't show up in production code by mistake.

It doesn't look like you will pass any arguments to log(), caller seems to provide anything you are looking for.

If you later check for production environment and set

sub log {}
[download]

then it will be optimized and not appear in the opcodes.

If you are still worried, use a name you can easily find and delete, like __LOG__, even a source filter doing this should be very safe.š

But please search the archives for older discussions, this is certainly not the first one.

Cheers Rolf

UPDATE

š) or even better, use Damian's approach from Smart::Comments and use a source filter only in testing mode to enable log() by deleting the '#' with s/;#LOG/;LOG;/g

s/a/b/ ;#LOG
[download]

In reply to Re^5: Module for Printing Line Numbers in Debug? by LanX
in thread Module for Printing Line Numbers in Debug? by QM

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks