menth0l has asked for the wisdom of the Perl Monks concerning the following question:

Hi, I want to change name of the caller module in runtime. For example: 
sub get_caller()
{
    print caller() . "\n";
}

sub dummy()
{
    my $dummy_module = "
        package DUMMY;
        sub wrapper {main::get_caller()};
        1;
    ";
            
    eval $dummy_module;
    my $dummy = {};
    bless $dummy, 'DUMMY';

    $dummy->wrapper();
    
}

get_caller();
dummy();

[download]
Output: 
main
DUMMY

[download]
Is it possible to 'disguise' caller module in easier, more elegant way? I need it to log messages in log4perl as if they were logged from totally different module...

Replies are listed 'Best First'.
Re: How to "disguise" caller
by moritz (Cardinal) on Feb 10, 2011 at 14:17 UTC
    I need it to log messages in log4perl as if they were logged from totally different module...

    I don't know your larger background, and I can't answer your question, but want to point out that when parts of your software is lying to other parts of the software, that's a strong indication that there's a larger problem in the design of your code.

    Maybe logging is abused for something it was never meant to? Or maybe it's really an XY Problem?

    Also, would you care to provide more background information about why this is necessary? I'm really curious.

    Perl 6 - second systems done right
[reply]
      Well, I got several objects of different classes which produce some data which is stored in a container object. When all workers finish, container renders reports and logs them. E.g. 
      $container->do_FooBarWork(); # Foo::Bar work 
$container->do_BazWhoWork(); # Baz::Who work
$container->createReport(); # renders report for each worker
$container->dumpReport(); # dumps all reports to log

      [download]
      Now all reports are logged by Container::dumpReport() method and thus log4perl can't tell which class produced which output. But if container class knew who produced what then it could log it "on behalf" of worker object. In other words i want to "tie" logged result to class that created it.
[reply]
[d/l]

        This might be an easier solution:

        Have a method in each of the worker classes that does the logging regarding its activity, and then call these methods from the container class. That way the reporting also becomes customizable by overriting the reporting method in an inheriting class.

        The container can still do some summary logging, if necessary.

        Perl 6 - second systems done right
[reply]

      I'd bet lunch he's mocking up output to feed a test without executing something undesirable, or something similar.

      In which case it would be... less bad.

      http://www.mpwilson.com/#pm
[reply]
Re: How to "disguise" caller
by belden (Friar) on Feb 10, 2011 at 15:50 UTC
    It looks like you're trying to substitute behavior of something, perhaps for testing. Can you post a more representative snip of "here's the code that's written", and "here's what I'm doing now to solve my problem"? Currently they're both kind of tied up together. :)
[reply]
Re: How to "disguise" caller
by DrHyde (Prior) on Feb 11, 2011 at 11:02 UTC
[reply]
[d/l]

Back to Seekers of Perl Wisdom