Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Re^3: Override printing to STDOUT/ERR

by learnedbyerror (Monk)
on Apr 15, 2018 at 18:36 UTC ( #1212942=note: print w/replies, xml ) Need Help??

in reply to Re^2: Override printing to STDOUT/ERR
in thread Override printing to STDOUT/ERR

You may want to consider using on of the logging frameworks, available on CPAN, as opposed to a print based approach

Log::Log4perl, Log::Any, Log::ger are examples that support directing output of the log statements to different locations based upon a category. A category is generally a package but can be explicitly set as desired.

Here an example from the Log::ger::Manual::Tutorial::05_Category tutorial

use Log::ger::Output Composite => ( outputs => { File => [ { conf => {path=>'/path/app.log'}, category_level => { Foo => 'off' }, }, { conf => {path=>'/path/foo.log'}, level => 'off', category_level => { Foo => 'trace' }, }, ], }, );


Replies are listed 'Best First'.
Re^4: Override printing to STDOUT/ERR
by bliako (Prior) on Apr 17, 2018 at 10:00 UTC

    lbe, I am just looking at these modules right now. It is great that one can separate log output depending on categories but it seems to me that they don't actually catch print statements and redirect them but rather handle their own logger messages.

    Ideally what I want is, given a perl program possibly using many modules, to run it and have every single print statement 1) redirected to file and 2) prepended by (filename,modulename,subname,linenumber). If I am given that program, it means I can clone it and replace all print statements with log statements but 1) what about print statements inside 3rd-party modules and 2) extra complication if bleached.

    What I am doing right now and works is 1) redirect STDOUT to file 2) tie STDOUT to a class so when any print is called on that filehandle, I intercept the call and prepend the caller's fingerprint all the way to the top of the frame (<main>).

    The module I mentioned works well but I had to extend it in order to handle STDERR and also for redirecting to a file (implementing OPEN/CLOSE).

    In case you have a suggestion: my current problem is what data structure to use for storing all these print statements' output so that, for example, I make queries like: what is the STDOUT for lines X-Y, filename Z or do not show me output for lines so and so or sub so and so or package so and so. The data is all there but structuring it in order to make these queries is my next stop. I am currently playing with tree. I will sure post a separate request about these problems.

    thanks, bliako

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1212942]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (2)
As of 2020-10-25 06:18 GMT
Find Nodes?
    Voting Booth?
    My favourite web site is:

    Results (249 votes). Check out past polls.