Evaluation order incompatiblity vs LambdaMOO

[visiblecode]

Recent* versions of JHCore have an $integration_utils:parse that relies on LambdaMOO evaluating the LHS of an assignment statement before the RHS. So:

"parse(list lists of objects and/or strings, verb_or_property)";
set_task_perms(caller_perms());
what = args[1];
voo = args[2];
result = {};
for l in (what)
result = {@result, {}};
for os in (l)
  if (msg = this:_parse(os, voo))
    if (msg)
      result[index = length(result)] = {@result[index], msg};
    endif
  endif
endfor
  if (!result[index = length(result)])
    result = listdelete(result, index);
  endif
endfor
return result; 

Will crash with E_VARNF on result[index = length(result)] = {@result[index], msg};, as the RHS of the assignment gets evaluated first, meaning that index won't be defined yet. The code's expecting the LHS to get evaluated first.