From svetosch@gmx.net Wed Jan 14 03:35:21 2009
From: Sven Schreiber <svetosch@gmx.net>
To: gretl-devel@gretlml.univpm.it
Subject: [Gretl-devel] Re: [Gretl-users] pre-release testing for gretl 1.8.0
Date: Wed, 14 Jan 2009 09:35:21 +0100
Message-ID: <496DA3C9.60201@gmx.net>
In-Reply-To: 771847.23591.qm@web50901.mail.re2.yahoo.com
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0759839782548704902=="

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

[taking this over to the devel-list]

Dear devels,

given that at least two new loop bugs have been reported in very recent
cvs versions (January 2009, one by me and the second one in this
thread), it seems to me that the recent under-the-hood-changes in that
area have the potential to produce other related bugs in the near future.

So maybe the loop stuff should be systematically tested before a new
release is made.

just a thought,
sven

Am 14.01.2009 07:59, Yuniarto Hadiwibowo schrieb:
> After I've checked all the setting, it seems that the local language is the problem. The local setting in my PC is Japan, but my laptop is English. By default, Gretl uses Japanese local language setting for my PC. The result is in English, no translation yet. So, in my confusion I thought that it is English. I don't know if changing the default to English is better. Thank you, I am sorry for this.
> 
> 
> Another matter is the index variable in loop. The following script works in 1.7.9 and previous cvs, but not in current cvs. The data contains variable named i (although it is not used in this script). If I change the index variable from i to k, it works. It seems that the scope of index variable is changed in the current cvs. I don't know which one is better.
> 
> <script>
> open adf_test
> loop foreach j nc c ct ctt gls --quiet
> loop foreach i employ prdefl gnp unemp armfrc pop --quiet
> adf 4 $i --$j --test-down
> lt_$i$j=$test
> lp_$i$j=$pvalue
> adf 4 $i --$j --difference --test-down
> dt_$i$j=$test
> dp_$i$j=$pvalue
> end loop
> end loop
> </script>
> 
> Yuniarto Hadiwibowo
> 
> 
> ----- Original Message ----
> From: Allin Cottrell <cottrell(a)wfu.edu>
> To: Gretl list <gretl-users(a)lists.wfu.edu>
> Sent: Wednesday, January 14, 2009 12:54:39 AM
> Subject: Re: [Gretl-users] pre-release testing for gretl 1.8.0
> 
> I've installed/uninstalled gretl many times on Windows PCs and
> haven't seen this sort of thing.  Are you sure you have the right
> permissions to perform the uninstall correctly?
> 
> Allin Cottrell
> 
> 
>       
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Gretl-users mailing list
> Gretl-users(a)lists.wfu.edu
> http://lists.wfu.edu/mailman/listinfo/gretl-users


--===============0759839782548704902==--


From cottrell@wfu.edu Wed Jan 14 19:56:39 2009
From: Allin Cottrell <cottrell@wfu.edu>
To: gretl-devel@gretlml.univpm.it
Subject:
 Re: [Gretl-devel] Re: [Gretl-users] pre-release testing for gretl 1.8.0
Date: Wed, 14 Jan 2009 19:56:38 -0500
Message-ID: <Pine.A41.4.58.0901141944080.422228@f1n11.sp2net.wfu.edu>
In-Reply-To: 496DA3C9.60201@gmx.net
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2541495424427563770=="

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

On Wed, 14 Jan 2009, Sven Schreiber wrote:

> given that at least two new loop bugs have been reported in very
> recent cvs versions (January 2009, one by me and the second one
> in this thread), it seems to me that the recent
> under-the-hood-changes in that area have the potential to
> produce other related bugs in the near future.
>
> So maybe the loop stuff should be systematically tested before a
> new release is made.

Thanks, Sven.  I've tested the new code on a fairly wide variety
of scripts.  The bug that you discovered was a localized parsing
issue, now fixed.  The "bug" that Yuniarto found was, as I said
subsequently, a bug fix.  Under the old scheme the loop index
variable was sui generis, but now it's a proper scalar variable,
which staves off various potential problems.  A side effect of
that is that you can't use as loop index an identifier that is
already claimed as the name of a series (or matrix).  But this is
already strongly implicit in gretl's variable-type system.

I certainly don't want to discourage further testing; but I'm
fairly confident that the current loop code is "right".

Allin.

--===============2541495424427563770==--


From svetosch@gmx.net Thu Jan 15 05:20:58 2009
From: Sven Schreiber <svetosch@gmx.net>
To: gretl-devel@gretlml.univpm.it
Subject:
 Re: [Gretl-devel] Re: [Gretl-users] pre-release testing for gretl 1.8.0
Date: Thu, 15 Jan 2009 11:20:59 +0100
Message-ID: <496F0E0B.9050400@gmx.net>
In-Reply-To: Pine.A41.4.58.0901141944080.422228@f1n11.sp2net.wfu.edu
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1860525744952948788=="

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

Allin Cottrell schrieb:
> On Wed, 14 Jan 2009, Sven Schreiber wrote:
> 
>> given that at least two new loop bugs have been reported in very
>> recent cvs versions (January 2009, one by me and the second one
>> in this thread), it seems to me that the recent
>> under-the-hood-changes in that area have the potential to
>> produce other related bugs in the near future.
>>
>> So maybe the loop stuff should be systematically tested before a
>> new release is made.
> 
> Thanks, Sven.  I've tested the new code on a fairly wide variety
> of scripts.  The bug that you discovered was a localized parsing
> issue, now fixed.  The "bug" that Yuniarto found was, as I said
> subsequently, a bug fix.  Under the old scheme the loop index
> variable was sui generis, but now it's a proper scalar variable,
> which staves off various potential problems.  A side effect of
> that is that you can't use as loop index an identifier that is
> already claimed as the name of a series (or matrix).  But this is
> already strongly implicit in gretl's variable-type system.
> 
> I certainly don't want to discourage further testing; but I'm
> fairly confident that the current loop code is "right".
> 
>

Fair enough, especially given that the assumption (two bugs in a short
period) turned out to be wrong...

I still plan to make minor adjustments to de.po quite soon (I wanted to
do it last night, but had networking problems), but those are certainly
not release stoppers.

cheers,
sven

--===============1860525744952948788==--