Fix eval and function constructor failing for object literals with __proto__ prop

[KurtGokhan]

Related to #598

Fixes weren't applied to Eval and Function Ctor before.

Edit after tests: Tolerant = true breaks other tests. Do you know what may be a better solution?

[lahma]

I quickly checked just one test case and its contents:

function testcase()
{
  try 
  {
    eval('"use strict"; var x = "\\17";');
    return false;
  }
  catch (e) {
    return (e instanceof SyntaxError);
  }
}
runTestCase(testcase);

So my hunch is that it's a strict mode issue. At least PerformEval has strictCaller parameter which you could use to choose between two different option setups (tolerant true/false), so maybe another static field for choosing between. Didn't dig deep into the issue so not sure.

[KurtGokhan]

I think this should be solved in Esprima.NET.

Basically, this should work: ({ __proto__: [] })

This should fail: ({ __proto__: [], __proto__: [] })

I will try to fix it.

[KurtGokhan]

Created sebastienros/esprima-dotnet#192

There is no need to change any code in Jint. Only tests.

But I noticed that by making Tolerant = true in the engine in this PR, some behaviors are not compliant with spec. Should we revert it? But it can be a breaking change.

[lahma]

Main branch has been updated with latest Esprima. Is there still an issue that we need to fix?

[KurtGokhan]

Let me test real quick.

[KurtGokhan]

Good to go. It is only tests.

[lahma]

Thanks for verifying!