From svetosch@gmx.net Fri May 23 08:57:49 2008
From: Sven Schreiber <svetosch@gmx.net>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] omit bug
Date: Fri, 23 May 2008 14:57:46 +0200
Message-ID: <4836BF4A.5050903@gmx.net>
In-Reply-To: alpine.LRH.1.10.0805220903550.435@ricardo.ecn.wfu.edu
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4317485365248540126=="

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

Am 22.05.2008 15:06, Allin Cottrell schrieb:
> On Thu, 22 May 2008, Sven Schreiber wrote:
> 
>> there seems to be a new bug introduced after 1.7.4; as always, I 
>> can provide more details later and/or file a bug report, but 
>> maybe this is already enough, and before I forget about it, here 
>> goes:
>>
>> In a script of ours, we have an "omit" test statement after a 
>> standard (OLS) estimation, but in between there are some other 
>> calculations ("scalar" and "matrix", so effectively "genr" I 
>> guess).
> 
> Please send a test case, I can't replicate this.  For example, the 
> following works fine:

Ok, it seems to be related to calling a user-defined function after 
estimation and before the restriction test; here is a demo script:

<script>
open denmark

function trivial(void)
result = 1
return scalar result
end function

ols LRM 0 LRY
scalar check = trivial()
omit LRY
</script>

This gives the mentioned error on today's CVS. I can't guarantee right 
now that this demo script works with 1.7.4, but our real-world script 
(where we noticed the bug) did.

In this case there is obviously an easy workaround (move the function 
call after the omit), but I can imagine cases where you want to use 
'restrict' with some value that you need to calculate in a function 
beforehand. So I'm inclined to think it's a bug.

thanks,
sven

--===============4317485365248540126==--