1 unicode identifier support (native and \u)
2 support unions (right now 0-1 fields parsed as struct)
3 \\\n escapes in strings aren't handled in the console
4 look into what String is, and whether to bridge it
5 think about bridging NSNumber with Number prototype
6 some JS callbacks don't use exception pointers at all...
7 a newline needs to not be allowed after a unary *
8 finish implementing default xml namespace statement
9 encode newlines in history for later reply (psql uses ^A)
11 consider replacing regex literals with constructors
12 https://bugzilla.mozilla.org/show_bug.cgi?id=98409
13 numerification needs to use specific precision values
14 https://bugzilla.mozilla.org/show_bug.cgi?id=5856
15 consider a mode where unicode string content is saved
16 https://bugzilla.mozilla.org/show_bug.cgi?id=274152
18 NSDictionaries that have NSNumber keys don't getProperty
19 errors in another process aren't displayed; to fix this, parse errors should get converted to exceptions and thrown
20 CYPoolTry/Catch now carefully save the exception after it /no longer needs the exception/... uhh... wtf?
21 throw CYJSError should probably be replaced with CYThrow() across the board
22 figure out what to do about global context refs: I really really want to retain the bastards
23 the concept of NULL pooling is entirely incorrect and sad... bad... evil... need to work on this... really