Instead, the name of the built-in function is append to the
error message ("Error in foo: ...").
Arguably, the convention of requiring EvalError messages
to start with the name of the function was a mistake, since
it's easy to forget, and easier to move the responsibility
to the stack trace printing logic, as we do here.
Instead, the name of the built-in function is append to the error message ("Error in foo: ...").
Arguably, the convention of requiring EvalError messages to start with the name of the function was a mistake, since it's easy to forget, and easier to move the responsibility to the stack trace printing logic, as we do here.