in reply to Print STDOUT and STDERR to file and to screen

I Can’t use external modules like: File::Tee, IO::Tee and so on

Whenever I hear someone say this, big red flags go up.

The module itself looks to be about 100 lines of code in a single file so I'm having a really hard time understanding what it is that could be keeping one from using it.

  • Comment on Re: Print STDOUT and STDERR to file and to screen

Replies are listed 'Best First'.
Re^2: Print STDOUT and STDERR to file and to screen
by cdarke (Prior) on Aug 03, 2009 at 03:37 UTC
    This is common in financial and defence installations that do not allow downloads. Controlled downloads are done under quarantine and thoroughly tested - a beauracratic process which takes time and written justification. An uncontrolled download could be a sackable offence.
[reply]
      That doesn't apply here.
[reply]

      Definitely doesn't apply here. What is the difference between coping the code from Perl Monks and copying from CPAN? None. Except for that in this case you're going to get better, easier to use code from CPAN.

      I've been doing this a long time, and when I hear someone say "I can't use a module", what they really are saying is "I don't know how to use a module".

[reply]

        I tend to agree with you but I think you underestimate how stick-stupid corporate bureaucracy can be. Another facet being that it can be very convenient to make everything against the rules. Then when you discover you don't like someone personally/politically...

[reply]
        He never said he can't use modules, he just can't use ones tha don't come with the default perl build. I too run into the very same issue ... my gov customer has 100's of workstations, and I can't code to something that would require them to install modules from CPAN. So you don't know what your talking about ...
[reply]

In Section Seekers of Perl Wisdom