From svetosch@gmx.net Mon Jan 22 10:33:44 2007
From: Sven Schreiber <svetosch@gmx.net>
To: gretl-devel@gretlml.univpm.it
Subject: [Gretl-devel] another function bug
Date: Mon, 22 Jan 2007 16:33:36 +0100
Message-ID: <45B4D950.5000107@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0331569234878258669=="

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

Some new bugs I have noticed:

- The most serious: the following example script adds a scalar
"determ_case" to the list of variables, which is completely unintended
and I don't see why it should be so, because it's just an internal
function parameter.

<script>
function vec_decomp (const list endogenous,  int ci_rank[1:10:1]), int
determ_case[1:5:3])

list result = null
loop foreach i endogenous
  series $i_SWP = i
  list result = result $i_SWP
endloop

return list result
end function

## test input:
open denmark
list endo = LRM LRY
list test2 = vec_decomp(endo, 1, 3)
</script>

- The other things are quite trivial: "const", "foreach" and "i" (index
variable) could maybe use some syntax coloring as well, and with "'" as
the transpose notation there are also syntax coloring problems. (It is
interpreted as a string delimiter.)

bye,
sven



--===============0331569234878258669==--


From r.lucchetti@univpm.it Mon Jan 22 12:06:08 2007
From: Riccardo (Jack) Lucchetti <r.lucchetti@univpm.it>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] another function bug
Date: Mon, 22 Jan 2007 18:06:09 +0100
Message-ID: <48472.193.205.135.4.1169485569.squirrel@mta01.univpm.it>
In-Reply-To: 45B4D950.5000107@gmx.net
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7576439029508231048=="

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


On Mon, January 22, 2007 16:33, Sven Schreiber wrote:
> Some new bugs I have noticed:
>
> - The most serious: the following example script adds a scalar
> "determ_case" to the list of variables, which is completely unintended
> and I don't see why it should be so, because it's just an internal
> function parameter.
>
> <script>
> function vec_decomp (const list endogenous,  int ci_rank[1:10:1]), int
> determ_case[1:5:3])

Sure it needs to be fixed, but isn't there an extra left parenthesis
after ci_rank?

>
> - The other things are quite trivial: "const", "foreach" and "i" (index
> variable) could maybe use some syntax coloring as well, and with "'" as
> the transpose notation there are also syntax coloring problems. (It is
> interpreted as a string delimiter.)

Yes!! I find it annoying too. The trouble is, telling the two uses of "'"
apart isn't exactly trivial: you need to parse the source to see if the
preceeding expression can be legitimately interpreted as a matrix. Not
easy.

Maybe it can be pseudo-fixed via the following hack: colour-code as
string only if you have 2 "'"s in a line (but then, it's quite possible
you have two transpositions in the same line; it just "fixes" the case
when you've only got one).


Riccardo (Jack) Lucchetti
Dipartimento di Economia
Facoltà di Economia "G. Fuà"
Ancona


--===============7576439029508231048==--


From cottrell@wfu.edu Mon Jan 22 13:31:24 2007
From: Allin Cottrell <cottrell@wfu.edu>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] another function bug
Date: Mon, 22 Jan 2007 13:31:24 -0500
Message-ID: <Pine.LNX.4.64.0701221235190.4978@ricardo.ecn.wfu.edu>
In-Reply-To: 45B4D950.5000107@gmx.net
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0930610324280792773=="

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

On Mon, 22 Jan 2007, Sven Schreiber wrote:

> - The most serious: the following example script adds a scalar 
> "determ_case" to the list of variables, which is completely 
> unintended and I don't see why it should be so, because it's 
> just an internal function parameter.

That one's fixed now too.

> - The other things are quite trivial: "const", "foreach" and "i" (index
> variable) could maybe use some syntax coloring as well, and with "'" as
> the transpose notation there are also syntax coloring problems. (It is
> interpreted as a string delimiter.)

As Jack points out, this one is tricky (I've just tried messing 
with various regexps to no avail).  However, in how many gretl 
contexts is 'string' acceptable?  Now that we're using ' as 
transpose, I'm inclined just to drop it from the syntax 
highlighting scheme.

Allin.

--===============0930610324280792773==--


From svetosch@gmx.net Tue Jan 23 03:47:59 2007
From: Sven Schreiber <svetosch@gmx.net>
To: gretl-devel@gretlml.univpm.it
Subject: Re: [Gretl-devel] another function bug
Date: Tue, 23 Jan 2007 09:47:52 +0100
Message-ID: <45B5CBB8.20801@gmx.net>
In-Reply-To: Pine.LNX.4.64.0701221235190.4978@ricardo.ecn.wfu.edu
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7121603557105912928=="

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

Allin Cottrell schrieb:
> On Mon, 22 Jan 2007, Sven Schreiber wrote:
>

>> - The other things are quite trivial: "const", "foreach" and "i" (index
>> variable) could maybe use some syntax coloring as well, and with "'" as
>> the transpose notation there are also syntax coloring problems. (It is
>> interpreted as a string delimiter.)
> 
> As Jack points out, this one is tricky (I've just tried messing with
> various regexps to no avail).  However, in how many gretl contexts is
> 'string' acceptable?  Now that we're using ' as transpose, I'm inclined
> just to drop it from the syntax highlighting scheme.
> 

I also couldn't think of an example where single-quoted strings are
actually allowed in gretl. If not, you're right, just drop it.

-sven


--===============7121603557105912928==--