Have STDOUT and STDERR write to a pipe, and the GUI program reads from the other end and updates the widget.

In Win32, pipes are not pseudoterminals and the program writing will know it's not the console and will buffer its output.

—John

one could, instead of using system, use fork/read/exec with a tied handle, which would allow perl constucts ... assuming the program to start was also perl. If the program is not perl, i agree with the pipe solution.

---

_{can't sleep clowns will eat me}
-- MZSanford

Um... It, uh, half works. :-)

#!/usr/bin/perl

use Tk;
$mw = MainWindow->new(-name => 'Test', -title => 'Test');
$text = $mw->Text();
$text->pack();

tie *STDOUT, 'Text::Handle', $text;
tie *STDERR, 'Text::Handle', $text;

print "Hello\n";
print STDERR "Hi\n";
warn "Doesn't work!  :(\n";

MainLoop;

package Text::Handle;
use Tie::Handle;
@ISA = qw/Tie::StdHandle/;

sub TIEHANDLE {
  my $class  = shift;
  my $widget = shift;
  return bless \$widget, $class;
}

sub PRINT {
  my $self = shift;
  $$self->insert('end', join('',@_));
}
[download]

Hrm. Looks like warn and die behave specially when it comes to STDERR. I can see good and bad points to that. :-/

It would be nice to have it more "push" oriented so that you didn't have to poll pipes (either non-blockingly, or in a seperate thread/process) but it looks like you're still going to need warn and die %SIG handlers. But that's why I wrote Tk::Carp ;-)

bbfu
Seasons don't fear The Reaper.
Nor do the wind, the sun, and the rain.
We can be like they are.

print "Hello\n";
print STDERR "Hi\n";

system "ls";  # what about this?
[download]

The issue is getting an external program to "see" the redirection.

Interesting about Warn. What exactly does it do specially with respect to STDERR?

—John