Opera parser monster eats unicode

Whilst writing my own parser I found weird things in Opera's JavaScript parser. I was testing what the various browsers allowed with unicode escapes and it turns out Opera seems more lax than others. My discovery began with the following code:

try {eval("\\u0066\\u0061\\u006c\\u0073\\u0065");} catch(e) {alert(e);}

What do you expect the undefined variable to be? It's a unicode encoded "false" hehe so we can have a variable called "false" if we use unicode escapes on Firefox but what about Opera? Well it's actually looking for a variable called "false5". Why? Because the JavaScript parser seems to be off by one when using eval with unicode escapes so it thinks the \u006 is actually \u0065 and thus the "5" is added onto the string.

Pretty cool, so what else can we do? Well, Opera seems a bit more lax than the other browsers when it comes to unicode escapes, for example this is perfectly legal:

\u=alert,u(1)

Pretty nuts right? You can use an incorrect unicode escape and the backslash gets ignored. Another example:

\u000x=alert;u000x(1)

And finally I leave you with this, you can make \u become uu when inside an eval statement:

window.__defineGetter__("uu",function() { alert(1) });eval("\\u");