commit | be8445d7e4b6122620c428877b51a27d464253d5 | [log] [tgz] |
---|---|---|
author | Roberto Ierusalimschy <roberto@inf.puc-rio.br> | Wed Jul 10 14:58:31 2019 -0300 |
committer | Roberto Ierusalimschy <roberto@inf.puc-rio.br> | Wed Jul 10 14:58:31 2019 -0300 |
tree | e0160895d105e5a3c20ec65c3196bffa042bd93f | |
parent | 3d296304ef14ac9a6d1fa9357541ddd9bb54722f [diff] |
Details In the generic for loop, it is simpler for OP_TFORLOOP to use the same 'ra' as OP_TFORCALL. Moreover, the internal names of the loop temporaries "(for ...)" don't need to leak internal details (even because the numerical for loop doesn't have a fixed role for each of its temporaries).