Re: [Gretl-devel] "start gretlcli.exe" vs. simple "gretlcli.exe" (on Windows)
On Tue, 10 Jan 2017, Sven Schreiber wrote:
Hi,
allow me to open a new thread for the shell command launching stuff here.
I'm following Allin's advice to use "start gretlcli" to background the
gretlcli process on Windows. The problem I'm facing right now (with the
latest snapshot) is that when I do (in the Windows cmd.exe console):
gretlcli.exe -b hansltemp.inp > testy.out
I get a good testy.out file written. However, when I do:
start gretlcli.exe -b hansltemp.inp > testy.out
The testy.out file gets overwritten as expected, but it is empty (0 bytes). I
know this might be a Windows issue instead of a gretl issue, but perhaps
somebody has an idea about what's going on nevertheless.
Hm. Even if it turns out to be an OS issue, it'd be good to delimit it
properly so we know what to say to users. To be on the safe side, I've
found myself relying more and more on the outfile command rather than the
OS piping features.
(I also have a totally different issue with a silently failing
bread()
function in a loop which somehow ignores part of the bundle contents, but I
leave that for later...)
That could be due to the bread() function being invoked when the buffer is
not yet committed to disk. We fixed that a few months ago in a way that
I thoughtwas definitive, but it obviously isn't :) If you could provide a
real test case, that would be very helpful.
-------------------------------------------------------
Riccardo (Jack) Lucchetti
Dipartimento di Scienze Economiche e Sociali (DiSES)
Università Politecnica delle Marche
(formerly known as Università di Ancona)
r.lucchetti(a)univpm.it
http://www2.econ.univpm.it/servizi/hpp/lucchetti
-------------------------------------------------------