Seems reasonable.

The parser will see the leading digit and assume that it is being presented with a numeric constant. The constant ends at the first non-numeric character (the "t").

The undefined action for an expression on the stack is to print it.

So, you get a "10" output to the screen, then the process chokes because is doesn't know what to do with the "to3" token.

I bet if you had a "to3" UDF it would have executed it.

Perhaps the "Function" declaration should complain about illegal function names.