# DO/NEXT vs. EVAL/NEXT vs. EVAL:STEP

**URL:** <https://revolt.metaeducation.com/forum/t/do-next-vs-eval-next-vs-eval-step/2291>\
**Category:** Naming\
**Created:** [September 21, 2024, 5:13pm UTC](https://revolt.metaeducation.com/forum/t/do-next-vs-eval-next-vs-eval-step/2291 "2024-09-21T17:13:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [September 21, 2024, 5:13pm UTC](https://revolt.metaeducation.com/forum/t/do-next-vs-eval-next-vs-eval-step/2291/1 "2024-09-21T17:13:59Z")

</div>

DO/NEXT was how you'd do a single step in historical Redbol

This is currently EVAL/NEXT (since DO is higher level and doesn't evaluate lists). But it hadn't occurred to me to question /NEXT...

But I realized that within the code, I call it **`Eval_Step_XXX()`**. And the level executor that runs a single evaluation step is called the **`Stepper_Executor()`**

So **`EVAL:STEP`** (new refinement notation) seems better to me.

```
>> [pos value]: eval:step [1 + 2 10 + 20]
== [10 + 20]

>> pos
== [10 + 20]

>> value
== 3

```
