On Wednesday 28 May 2008, Tim Hoffmann wrote:
> I am calling wgnuplot from an external program. Since there is no error
> stream attached one cannot receive error messages.
Errors are sent to stderr, the usual error stream. In a normal operating
environment (which may exclude MSWindows) you can receive the
messages just fine.
> The exit code just
> indicates that there is an error but not which.
The current CVS version also stores the most recent error message in the
variable GPVAL_ERRMSG. You can print it to a file if you want to.
> Therefore it would help,
> if there was an option to write errors to a file, e.g.:
> wgnuplot -log error.log
> I think it should be quite simple. One could intercept the error
> messages in MyFPrintF and similar functions.
> Before starting to implement, I would like to have some comments on the
> idea form more experienced gnuplot developers.
I am not sure there are any such people, with regard to Windows development.
I gather that the Windows user interface (by which I mean Windows itself,
not the gnuplot GUI) is fundamentally different from the stdin/stout/stderr
model used by gnuplot and pretty much all other unix or C programs.
(on the road)