[FIXED][3.0] Eval usage

[lightglitch]

I'm wondering why do you still (in version 3) use the eval function is several parts of the code instead of using always the same function to parse JSON.

For example in the JSONReader:

    readResponse : function(response) {
        var json = response.responseText;
        var o = eval("("+json+")");
        if(!o) {
            throw {message: "JsonReader.read: Json object not found"};
        }
        return o;
    }

Why don't you just use:

        var o = Ext.decode("("+json+")");

[stever]

Yeah, when I mentioned it before I forgot to mention readResponse as well as read...

[evant]

Mostly just an oversight, it doesn't really affect much, but it would be nice to fix up.

[lightglitch]

Yeah, when I mentioned it before I forgot to mention readResponse as well as read...

I missed your thread, but I just give that as an example.

If you search for eval in ext-all-debug.js it's used in much more places and if the Ext.decode already takes in account the browser support for JSON, should be used everywhere.

Mostly just an oversight, it doesn't really affect much, but it would be nice to fix up.

Agree.

[evant]

In a lot of places we still need to use eval(), the only outstanding place where it should use decode() is in the JsonReader, which I've just committed.