On Wed, Jul 19, 2023 at 9:37 AM Sven Schreiber
<sven.schreiber(a)fu-berlin.de> wrote:
this is with a July-3rd snapshot, and what strikes me as quite strange
behavior:
<hansl>
nulldata 20
series check = 0
check[1] = NA
check[10] = 1
loop tau = 1..$nobs
eval check[tau] # first with NA as expected
if check[tau] == 1
print tau # expect only 10, get 1 and 10
endif
endloop
</hansl>
Trying "if NA == 1" on the console (or also "if check[1] == 1") gives
an
"indeterminate" error message, which seems correct. Only inside the loop
does it act weirdly.
That's now fixed in git. The loop should fail with the "indeterminate"
error message at tau = 1, and now it does.
In the case where we had just compiled an "if" condition (which occurs
on the first iteration of a loop) we were returning "result != 0".
That's often the right thing to do, but not when the result is NA.
Allin