Revision: 7292 Author: [email protected] Date: Thu Dec 10 15:16:44 2009 Log: Edited wiki page through web user interface. http://code.google.com/p/google-web-toolkit/source/detail?r=7292
Modified: /wiki/NullIsUndefined.wiki ======================================= --- /wiki/NullIsUndefined.wiki Wed Dec 9 12:01:12 2009 +++ /wiki/NullIsUndefined.wiki Thu Dec 10 15:16:44 2009 @@ -24,7 +24,7 @@ = The Solution = Let both `null` and `undefined` be treated equally in generated Javascript code. If they are treated equally, those writing JSNI methods will no longer be required to coerce all return values to `null` (this will still be necessary for non-String primitive types). -In hosted-mode, this can be dealt with by simply coercing `undefined` return values to `null` in JsValueGlue. In web-mode, the generated Javascript code will simply need to ensure that all generated constructs will work properly in the presence of either `null` or `undefined`. +In development mode, this can be dealt with by simply coercing `undefined` return values to `null` in JsValueGlue. In production mode, the generated Javascript code will simply need to ensure that all generated constructs will work properly in the presence of either `null` or `undefined`. = Details = The only Java expression affected by this change will be identity comparison for Object types (e.g. `Object a,b; if (a == b)`). -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
