Bug #16757 for Log-StdLog: Feature Request, Output to STDOUT?

Tue Dec 27 18:54:57 2005 pansy [...] jeffery.martin.name - Ticket created

Date:	Tue, 27 Dec 2005 17:54:18 -0600 (CST)
Subject:	Feature Request, Output to STDOUT?
From:	"Jeffery Martin" <pansy [...] jeffery.martin.name>
To:	bug-log-stdlog [...] rt.cpan.org

It would be nice if I could specify STDOUT as the output file. Like this: use Log::StdLog { level => 'warn', file => "STDOUT" }; or use Log::StdLog { level => 'warn', file => STDOUT }; I don't really care how I am forced to specify it, as long as I could. I've tried both ways without success.

Thu Feb 09 18:25:57 2006 damian [...] conway.org - Correspondence added

Subject:	Re: [cpan #16757] Feature Request, Output to STDOUT?
Date:	Fri, 10 Feb 2006 10:25:06 +1100
To:	bug-Log-StdLog [...] rt.cpan.org
From:	Damian Conway <damian [...] conway.org>

Jeffery Martin via RT wrote: Show quoted text

> It would be nice if I could specify STDOUT as the output file. Like this: > > use Log::StdLog { level => 'warn', file => "STDOUT" }; > > or > > use Log::StdLog { level => 'warn', file => STDOUT }; > > I don't really care how I am forced to specify it, as long as I could. > I've tried both ways without success.

The module can be loaded so that it writes to a specific filehandle rather than to a named file. You need to use the (undocumented) 'handle' option rather than 'file': use Log::StdLog { level => 'warn', handle => \*STDOUT }; (Yes, I'll fix the lack of documentation for the next release ;-) Thanks, Jeffery. Damian

Thu Feb 09 18:26:00 2006 The RT System itself - Status changed from 'new' to 'open'