The behaviour has now changed to something different but also wrong: > ":4\x[308]a".EVAL a => 0
It should yield either a syntax error or the same thing as ":4a". Given that "4\x[308]" is not being accepted as a digit in term context or in Str.Int coercion, it should presumably yield a syntax error here. -zefram
