"parseLenient *only* uses eval(), not only as a fallback. ................."
I went into the source code and took a look at the parseLenient method. You are correct. parseLenient always uses eval(). The following is the code snippet that confirmed this fact for me: " [email protected]::escapeJsonForEval(Ljava/lang/String;)(json)............". Thanks for correcting my premise. Now, the natural question that popped in my mind is: Lets say there is a scenario where* the JSON to be parsed is totally trusted * . In such a case , I am trying to find out how parseLenient compares with parseStrict( *in terms of raw speed*) for new browsers that have native JSON support(IE8+, FF4 etc) Going by the following posts by Mozilla and Microsoft, it seems like native JSON would be the way to go because they claim that the native JSON is much faster and it sounds like it is only gonna improve over time: http://blog.mozilla.com/webdev/2009/02/12/native-json-in-firefox-31/ http://blogs.msdn.com/b/ie/archive/2008/09/10/native-json-in-ie8.aspx Any thoughts are much appreciated. thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
