b1ad2a1f61
Preform the following renames: * |reportedPos| -> |savedPos| (abstract machine variable) * |peg$reportedPos| -> |peg$savedPos| (variable in generated code) * |REPORT_SAVED_POS| -> |LOAD_SAVED_POS| (instruction) * |REPORT_CURR_POS| -> |UPDATE_SAVED_POS| (instruction) The idea is that the name |reportedPos| is no longer accurate after the |location| change (seea the previous commit) because now both |reportedPos| and |currPos| are reported to user code. Renaming to |savedPos| resolves this inaccuracy. There is probably some better name for the concept than quite generic |savedPos|, but it doesn't come to me. |
||
|---|---|---|
| .. | ||
| generate-bytecode.spec.js | ||
| helpers.js | ||
| remove-proxy-rules.spec.js | ||
| report-infinite-loops.spec.js | ||
| report-left-recursion.spec.js | ||
| report-missing-rules.spec.js | ||