Huh? Are you confusing ...

No confusion here. The bookkeeping overhead (pushing a marker onto the return stack, though I recall eval doing a bit more than that) is on par with creating a temporary variable. In my mind, at least, that cancels any performance objections about using a temporary variable.

eval'ing a string would be nuts, and I give you credit for not being that nuts.