[perl #132008] Term::ReadLine generates empty &STDERR files

On Fri, 01 Sep 2017 03:13:59 GMT, blgl@stacken.kth.se wrote:
> Quoth Todd Rinaldo:
> > The problem is that redirecting file handles to STDERR (open (my $fh,
> > ">&STDERR)) cannot be done as a 3 arg open or it'll actually try to
> > write to that file.
> 
> Yes, it can!
> 
>     open(my $fh, ">&", \*STDERR)
> 
> Getting Term::ReadLine to use this may involve breaking compatibility,
> since the findConsole method assumes 2-arg open.  Is findConsole ever
> called from outside the Term::ReadLine::* space?
> 
> 

findConsole is clearly documented, so we should assume that it's callable from outside that space.

#####
"findConsole"
returns an array with two strings that give most appropriate names for files for input and output using conventions "<$in", ">out".
#####

> /Bo Lindbergh


-- 
James E Keenan (jkeenan@cpan.org)

---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=132008

• [perl #132008] Term::ReadLine generates empty &STDERR files by James E Keenan via RT
• [perl #132008] Term::ReadLine generates empty &STDERR files by Todd Rinaldo
• Re: [perl #132008] Term::ReadLine generates empty &STDERR files by Bo Lindbergh
• [perl #132008] Term::ReadLine generates empty &STDERR files by James E Keenan via RT