7:39 a.m.
Hi,
not sure why the following fails, given the documentation of 'argname':
<hansl>
function void ch(matrix m[null], string s[null])
if exists(m)
eval argname(m)
elif exists(s)
eval argname(s)
endif
end function
string s_in = "hey"
ch(, s_in) # error, expect "s_in"
ch(, "hey") # expect "" (anonymous), got error (once we get here)
</hansl>
This is with April 25's snapshot on Windows.
thanks
sven
5:28 p.m.
On Thu, 2 May 2019, Sven Schreiber wrote:
not sure why the following fails, given the documentation of
'argname':
<hansl>
function void ch(matrix m[null], string s[null])
if exists(m)
eval argname(m)
elif exists(s)
eval argname(s)
endif
end function
string s_in = "hey"
ch(, s_in) # error, expect "s_in"
This is due to an ambivalence specific to string variables. When gretl
finds
eval argname(s)
are we supposed to take the argument as the value of the string
variable named "s" (if there is one), or as the string literal "s"?
What happens at present is the former, so the question becomes:
What's the argname of "hey"? Hence the failure. If the argname check
is given as
eval argname("s")
it will work.
Allin
6:19 p.m.
On Thu, 2 May 2019, Allin Cottrell wrote:
On Thu, 2 May 2019, Sven Schreiber wrote:
> not sure why the following fails, given the documentation of 'argname':
>
> <hansl>
> function void ch(matrix m[null], string s[null])
> if exists(m)
> eval argname(m)
> elif exists(s)
> eval argname(s)
> endif
> end function
>
> string s_in = "hey"
> ch(, s_in) # error, expect "s_in"
This is due to an ambivalence specific to string variables.
Well, I now think this (mis)behavior is new, fallout from my recent
addition of an optional second argument to argname(). I'll work on a
fix.
Allin
9:42 p.m.
On Thu, 2 May 2019, Allin Cottrell wrote:
On Thu, 2 May 2019, Allin Cottrell wrote:
> On Thu, 2 May 2019, Sven Schreiber wrote:
>
>> not sure why the following fails, given the documentation of 'argname':
>>
>> <hansl>
>> function void ch(matrix m[null], string s[null])
>> if exists(m)
>> eval argname(m)
>> elif exists(s)
>> eval argname(s)
>> endif
>> end function
>>
>> string s_in = "hey"
>> ch(, s_in) # error, expect "s_in"
>
> This is due to an ambivalence specific to string variables.
Well, I now think this (mis)behavior is new, fallout from my recent addition
of an optional second argument to argname(). I'll work on a fix.
Now fixed in git and snapshots. Here's the test script that I'm
adding to my test set so this won't go wrong again unnoticed.
<hansl>
function void strcheck (string s[null])
if exists(s)
eval argname(s, "defaultname")
else
print "no arg, OK"
endif
end function
function void matcheck (matrix m[null])
if exists(m)
eval argname(m, "defaultname")
else
print "no arg, OK"
endif
end function
string main_s = "hey"
strcheck(main_s)
strcheck("lucky")
strcheck()
matrix main_m = I(3)
matcheck(main_m)
matcheck(I(2))
matcheck()
</hansl>
Allin
2060
days inactive
2061
days old
4 comments
2 participants
participants (2)
-
Allin Cottrell -
Sven Schreiber