note TimToady I would consider it a bug that <code>==</code> can be parsed as <code>= =</code>, so you shouldn't depend on that. On the other hand, the <code>for</code> will not require parens, though it will require a space before the opening bracket. And <code>@l.pop</code> would be shorter than the function form. Then again, you eventually ought to be able to do the whole thing with <code> print reverse=<>; </code> 438876 438941