Published October 17, 2026 | Version v1

Learning from esolangs: COMEHERE for better testing

Authors/Creators

  • 1. Temper Systems, Inc.

Description

Presentation and extended abstract from LIVE 2026.

Abstract

Software testing can be hard. We've got IDEs, time travelling debuggers, and static analyzers but printf debugging is still a tried and true technique.

Imagine you're on the trail of a vexing bug; you suspect you know which function is responsible. Well, you can add debugging code, but you still have to get the program to go there; if the function is nested, there's no name main() can call to get there. And you can't just GOTO that code because it's harmful. Luckily the COMEFROM language solved that problem by allowing code at the destination to initiate a transfer of control.

What COMEFROM didn't solve was constructing the context necessary to figure out what's going on deep in the guts of your program. Instead, when you're hacking the suss function, just say COMEHERE:with(<context>).

I'm demoing a variant of JavaScript that adds COMEHERE to automatically drive control deep into a function to make interactive testing and debugging easy.

If you want your programming language to be easy to interactively debug or would like a semantics that allows turning the results of that interactive debugging into unit tests for implementation details deep inside nested functions that can specify inputs to outer function calls, then COME_ON_OVER to my talk!

Files

Learning from esolangs - COMEHERE for better testing.mp4

Files (19.8 MB)

Name Size
md5:ba165071a4f575d56928fecfdcd7ebf3
7.9 kB Download
md5:8b6c382218b6d8a32e4894ec7cc0672b
19.8 MB Preview Download