4:44 p.m.
Dear Gretl Team,
I think I found a small error in Hansl when someone insert commas in
the end of the comment line. Please take a look at the following code
to check this.
<hansl>
open australia.gdt
list vars = dataset
lags 2 ; vars
list list1 = null # If I terminate this comment line WITH a comma,
list list2 = null # I get an error (in the following loop) saying
# list2_ati does not exist.
loop i=1..2 --quiet
list list1 = list1 || PAU_$i
loop j=1..2 --quiet
list list2 = list2 || PUS_$j
endloop
endloop
list list1 = null # If I terminate this comment line WITHOUT a comma
list list2 = null # I do not get the error saying list2 does not exist.
loop i=1..2 --quiet
list list1 = list1 || PAU_$i
loop j=1..2 --quiet
list list2 = list2 || PUS_$j
endloop
endloop
list list1 print
list list2 print
</hansl>
Also I would like to make a suggestion: In my humble opinion, the
syntax to print list elements is not so intuitive and it looks like
very different from the other uses of the "print" command. My
suggestion is use something like this:
print list1 --names
or
print list1 --varnames
Best regards,
Henrique Andrade
5:56 p.m.
Am 07.11.2012 17:44, schrieb Henrique Andrade:
Dear Gretl Team,
I think I found a small error in Hansl when someone insert commas in
the end of the comment line. Please take a look at the following code
to check this.
<hansl>
open australia.gdt
list vars = dataset
lags 2 ; vars
list list1 = null # If I terminate this comment line WITH a comma,
list list2 = null # I get an error (in the following loop) saying
# list2_ati does not exist.
loop i=1..2 --quiet
list list1 = list1 || PAU_$i
loop j=1..2 --quiet
list list2 = list2 || PUS_$j
endloop
endloop
list list1 = null # If I terminate this comment line WITHOUT a comma
list list2 = null # I do not get the error saying list2 does not exist.
loop i=1..2 --quiet
list list1 = list1 || PAU_$i
loop j=1..2 --quiet
list list2 = list2 || PUS_$j
endloop
endloop
list list1 print
list list2 print
</hansl>
Also I would like to make a suggestion: In my humble opinion, the
syntax to print list elements is not so intuitive and it looks like
very different from the other uses of the "print" command. My
suggestion is use something like this:
I agree on that. I'm also in favor of
the '--' method
print list1 --names
or
print list1 --varnames
Best regards,
Henrique Andrade
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
6:01 p.m.
On Wed, 7 Nov 2012, Henrique Andrade wrote:
I think I found a small error in Hansl when someone insert commas in
the end of the comment line. Please take a look at the following code
to check this.
<hansl>
open australia.gdt
list vars = dataset
lags 2 ; vars
list list1 = null # If I terminate this comment line WITH a comma,
list list2 = null # I get an error (in the following loop) saying
# list2_ati does not exist.
loop i=1..2 --quiet
list list1 = list1 || PAU_$i
loop j=1..2 --quiet
list list2 = list2 || PUS_$j
endloop
endloop
[...]
Hmm, you're right. And the same thing would happen if the line
ended with a backslash or left parenthesis. We guarded against
interpreting comma (etc.) as indicating line continuation if
the command line in question started with the comment
character '#' (after dropping any leading white space), but
we didn't handle properly the case where a #-comment follows a
command. That's now fixed in CVS.
Also I would like to make a suggestion: In my humble opinion, the
syntax to print list elements is not so intuitive and it looks like
very different from the other uses of the "print" command. My
suggestion is use something like this:
print list1 --names
or
print list1 --varnames
That seems like a reasonable suggestion.
Allin Cottrell
10:14 p.m.
On Wed, 7 Nov 2012, Henrique Andrade wrote:
Also I would like to make a suggestion: In my humble opinion, the
syntax to print list elements is not so intuitive and it looks like
very different from the other uses of the "print" command. My
suggestion is use something like this:
print list1 --names
or
print list1 --varnames
Actually it's not so easy to arrange that. The thing is that
lists are basically "transparent" to gretl commands: they
automatically cash out to their membership. And option flags
are generally used to inflect how a command is executed, not
to change radically how it is parsed, as would have to happen
here.
But here's an alternative you might like:
eval varname(list1)
This now works in CVS/snapshots. It should have worked before
but there was a bug in "eval" for handling anonymous strings.
Allin Cottrell
10:16 a.m.
Am 08.11.2012 23:14, schrieb Allin Cottrell:
On Wed, 7 Nov 2012, Henrique Andrade wrote:
> Also I would like to make a suggestion: In my humble opinion, the
> syntax to print list elements is not so intuitive and it looks like
> very different from the other uses of the "print" command. My
> suggestion is use something like this:
>
> print list1 --names
>
> or
>
> print list1 --varnames
Actually it's not so easy to arrange that. The thing is that
lists are basically "transparent" to gretl commands: they
automatically cash out to their membership. And option flags
are generally used to inflect how a command is executed, not
to change radically how it is parsed, as would have to happen
here.
But here's an alternative you might like:
eval varname(list1)
Since I really like the 'eval' command I also like this
alternative :-)
This now works in CVS/snapshots. It should have worked before
but there was a bug in "eval" for handling anonymous strings.
Allin Cottrell
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
4184
days inactive
4186
days old
4 comments
3 participants
participants (3)
-
Allin Cottrell -
Henrique Andrade -
Pindar