Hi,

I'm want some very simple logging that given something like 

file.pl
20: log_error( "a error msg", $level )

[download]
prints the equivalent of doing this on the same line 
print STDERR "a error msg:" . __FILE__ .  __LINE__ 
if $level >= THRESHOLD;

[download]
i.e. It prints the line number where the function was called, not the line number from inside the log_error subrountine.

Stuck on how to do this

1. Printing the line number where the log_error was called without including it in the argument

2. I'd like anything < THRESHOLDfor the current run to be removed at compile time if possible to avoid a performance hit...not sure if can really do that...or if it makes a difference.

This application has to be very fast I don't need much and prefer to not use any log modules if I don't need to.

Any help appreciated thanks so much!

Kosun

In reply to fast logging showing calling position.. by kosun

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.