1 unicode identifier support (native and \u)
2 support unions (right now 0-1 fields parsed as struct)
3 look into what String is, and whether to bridge it
4 think about bridging NSNumber with Number prototype
5 some JS callbacks don't use exception pointers at all...
6 a newline needs to not be allowed after a unary *
7 finish implementing default xml namespace statement
8 encode newlines in history for later replay (psql uses ^A)
10 consider replacing regex literals with constructors
11 https://bugzilla.mozilla.org/show_bug.cgi?id=98409
12 numerification needs to use specific precision values
13 https://bugzilla.mozilla.org/show_bug.cgi?id=5856
14 consider a mode where unicode string content is saved
15 https://bugzilla.mozilla.org/show_bug.cgi?id=274152
17 NSDictionaries that have NSNumber keys don't getProperty
18 errors in another process aren't displayed; to fix this, parse errors should get converted to exceptions and thrown
19 CYPoolTry/Catch now carefully save the exception after it /no longer needs the exception/... uhh... wtf?
20 throw CYJSError should probably be replaced with CYThrow() across the board
21 figure out what to do about global context refs: I really really want to retain the bastards
22 the concept of NULL pooling is entirely incorrect and sad... bad... evil... need to work on this... really
23 NSArray's .toString() and .toLocaleString() fail hard, as Array.prototype.to*String are Array-specific
24 applyOnMainThread, when done at console, loops the cyonifier
25 special work needs to be done to correctly handle the "arguments" symbol: Declare("arguments", ...Special)
26 at the Program level I seem to be eating away all of the var statements
27 function pointers are ?; note that blocks are currently block_P = '?'
28 I should probably attempt to use the auto_ flag somehow to not do contexts_ push when compiling
29 Object_callAsFunction_toCYON should be implemented