1
edit
Changes
→Phase 10: Apply Changes per Code Review 4
* Send patch to NexJ for review
===Phase 10: Apply Changes per Code Review 4 ===
*The m_tokenValue used in some of the error messages won’t always be populated. For example, in parseArray(), m_tokenValue is used, but it will only be valid if the current token is TOKEN_ATOM.
*The boolean.invalidateToken error message can be removed and you can use just err.parse.unexpectedToken instead, as one doesn’t know for certain that the input is a Booldean. Same for null.invalidateToken and number.invalidToken.
* parseObject(): the if (sKey == null) check can never succeed, because instanceof should return false if its argument is null.
==Links==
'''JSON''' <br/>
http://www.json.org <br/>
