I stumbled across a glitch with error messages occurring in nested
functions. I'm reporting it not per se, but because it might hint at a
deeper issue with nested functions, given a history of subtle flakiness
with function scopes and such -- I just don't know.
Here are the error messages:
? list gapstuff = getSWPDeltaout(endo,rexo,uexo, \
matrix Bstar0 += B2+
Das Symbol 'B2' ist nicht
> matrix Bstar$j += B$i+alpha*beta'
> loop for (i=j+1;i<=p-1;i+=1)
error in function get_si
matrix S = getS(shortruncoeffs,betaext,p,withconst)
matrix si = get_si(vecshrun,betaext,p,numrexo,withconst,whichvar)
Fehler bei Skriptausführung: Stopp
list gapstuff = getSWPDeltaout(endo,rexo,uexo,
The error itself is due to yours truly, that's not the point and the
error message about 'B2' is correct.
But notice that the error occurs in function getS(), called by get_si()
which in turn is called by getSWPDeltaout(). However, gretl reports only
the first two steps of the cascade, "error in function getSWPDeltaout"
and "error in function get_si".