Re: pgnuplot.exe flow control

[Tait <gnu...@t4...>]

Hans-Bernhard Bröker <HBBroeker_t-online.de> said (on 2008/03/19):
> It's known that fast inputs into pgnuplot will overrun its input pipe,
> and we don't know what to do about that.
> ...
> If your source application is Perl, it's almost certainly better to
> redirect to gnuplot from inside the Perl script.  That way your script
> has actual control over the pipe.

Thanks to both of you for your replies. I am actually opening the handle to
pgnuplot from within Perl... it's just easier to demonstrate the concept
in an email using |. I can tell Perl to autoflush, but I still have the
problem that Perl is too fast for pgnuplot. Is there any way for the data
provider (the thing dumping into the pipe) to know when pgnuplot/gnuplot
is ready for more input?

I don't have much experience with interprocess communication, so I don't
know how these kinds of things are usually handled, but it seems like a
problem that must have been solved many times over.


Tatsuro MATSUOKA <tmacchant3_yahoo.co.jp> said (on 2008/03/19):
> The wgnuplot_pipes.exe is entirely different from the pgnuplot
> It allows that
>     plot '< awk -f awkscript.awk'

Is there a reason why the wgnuplot_pipes behavior is not simply the 
default in wgnuplot.exe?