develooper Front page | perl.perl5.porters | Postings from May 2013

[perl #118003] "perl single step doesn't write steps to stderr"

Thread Next
Linda Walsh via RT
May 26, 2013 18:31
[perl #118003] "perl single step doesn't write steps to stderr"
Message ID:
On Wed May 15 19:39:40 2013, wrote:
> It works better if you deal in *solutions*. 
The patch would redirect output to stderr if runnonstop is set.

Note -- this fixed a unreported bug in the code -- as above, runnonstop
is set when there is no "/dev/tty".... 

Yet less than a page below that, "/dev/tty" is used for default output.

Checking if runonstop is set and setting output /dev/stderr make perl's
trace facility work the same as most other trace facilities users are
familiar with.  It also looks better since setting the output to
/dev/tty when above you just checked if it existed, and, at the point
output is assigned to /dev/tty, perl should be using 'runnonstop' as a
determiner of whether or not to use /dev/tty. 

Anyway, patch for with an update to its pod is attached.

(I actually went in to try to fix the lack of history... but then
remembered this problem...)  Such a simple change -- and fixing another
bug at the same time!  Worked the first time (which is a first for my
perl coding of late).

via perlbug:  queue: perl5 status: open

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About