True - we have a comment in there that you need to include json2.js for iOS 3.x. Soon however in 2.0, we are not supporting iOS 3.x, so this will not be applicable anymore.
On Fri, Jun 1, 2012 at 6:18 PM, Jesse <[email protected]> wrote: > I know it is always available, just meant that if it is not built into the > browser on a version we support, then we need to add a note that the > developer needs to bundle/include it in their html. > I believe we still have a comment in the generated html code for iOS for > older versions. > > On Fri, Jun 1, 2012 at 6:00 PM, Patrick Mueller <[email protected]> wrote: > > > On Fri, Jun 1, 2012 at 8:19 PM, Jesse <[email protected]> wrote: > > > > > If JSON.parse is available then definitely use it! > > > > > > > JSON.parse is always available, worse case is adding it yourself: > > > > https://github.com/douglascrockford/JSON-js/blob/master/json2.js > > > > (note, this doesn't even have Crock's "do not use for evil" clause! (I > > think the Java version does though)) > > > > Unless there is a size/speed issue with using this code, if you don't > have > > JSON built in, please use it - or something equivalent. > > > > I guess I'm curious to see if folks have been dependent on eval() for > other > > reasons. > > > > -- > > Patrick Mueller > > http://muellerware.org > > > > > > -- > @purplecabbage > risingj.com >
