From svetosch@gmx.net Mon Sep 17 05:59:04 2007
From: Sven Schreiber <svetosch@gmx.net>
To: gretl-devel@gretlml.univpm.it
Subject: [Gretl-devel] parser bug
Date: Mon, 17 Sep 2007 09:59:04 +0100
Message-ID: <46EE41D8.5040704@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6041031658592826021=="

--===============6041031658592826021==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi,
I've diagnosed a bit more a bug I briefly mentioned a while ago; here's
what happens:

I have the following minimal example script:

<script>
open denmark
outfile --write "@userdir/optionerrortest.py"
print "        tracestats = -teff * log(1-evals).cumsum()"
outfile --close
</script>

I'm expecting a file optionerrortest.py with the contents:
<expected>
        tracestats = -teff * log(1-evals).cumsum()
</expected>

but I effectively get the following contents:

<actual>
? print "        tracestats = -teff * log(1-evals).cumsum()"
Invalid option '-e'

Fehler bei Skriptausführung: Stopp
> print "        tracestats = -teff * log(1-evals).cumsum()"
</actual>

It actually seems to be a newly introduced behavior, because the test
script 'py4gretl_test.inp' that you (Allin) had requested in May fails
for the same reason, where it ran fine back in May. (It clearly was a
good idea of you to ask for that test scenario.)

/sven


--===============6041031658592826021==--