Going through the latest changelog, I see that there was a mention of this
issue.

13-04-04  A bug in which an unset variable error with set -u on did not
      terminate the current script has been fixed.

Trying to isolate the fix for this, I saw that in the varsub() function in
macro.c,
there is a check added for this case.

        if(!v && sh_isoption(mp->shp,SH_NOUNSET))
        {
            d=fcget();
            fcseek(-1);
            if(!strchr(":+-?=",d))
                errormsg(SH_DICT,ERROR_exit(1),e_notset,ltos(c));
        }

But even with this change, the issue is still happening.

Tracing the code, I see that the variable d will be '\0' and this is being
checked in the strchr
function, causing strchrto return true. Hence the errormsg function is not
being called.

Could someone please confirm whether this is the issue.

Thanks,
Lijo
_______________________________________________
ast-developers mailing list
ast-developers@lists.research.att.com
http://lists.research.att.com/mailman/listinfo/ast-developers

Reply via email to