Running Code

Tape has two execution paths from the same source code.

Interpret via VM

bash
tape run script.tape -I stdlib

Lowers the source to TAC IR and interprets it directly — there is no bytecode encoding step. Fast iteration, no build step.

Compile to native

bash
tape build app.tape -I stdlib -o app.exe

Compiles the same IR to a native executable — x86-64 or ARM64, depending on the target. No interpreter overhead.

-I stdlib points at the standard library shipped in the release archive; any program with an import needs it.

Which to use

CommandBest for
tape runDevelopment, scripts, quick iteration
tape buildRelease builds, deployment, performance

Both paths produce identical behavior — the same source, same semantics, same results. The VM exists for development speed; native exists for deployment performance.

Last modified: