220584 - Script() result has no prototype and scope chains

Status: RESOLVED FIXED

(Rhino Graveyard :: Core, defect)

Description

[Igor Bukanov]

When Script object is called as a function, its result does not have properly
initialized prototype and scope chains so various Script.prototype methods
including toString does not work.

For example, calling 
var s = Script("1;");
print(s.__proto__ != null)
print(s.__parent__ != null)
print(s)

gives 
false
false
js: "<command>", line 3: uncaught JavaScript exception:
java.lang.RuntimeException: org.mozilla.javascript.PropertyException:
Constructor for "TypeError" not found.

instead of expected: 
true
true

1;

This is a semi-regression in rhino CVS compared with Rhino 1.5 Release 4.1 since
there the bug is only present in the interpreter.

Note that calling Script as a constructor works without any problems.

Comment 1

[Igor Bukanov]

The propagation of the bug into the optimizer happens during changes to make
optimizer to generate single class when made code for Script initialization
shared between compiler and interpreter. 

Comment 2

[Igor Bukanov]

Attachment: Fix: initialize scope and prototype for Script instances in NativeScript.jsConstructor

If Script is called as a constructor, it will get the proper parent and
prototype from the generic code to initialize newly constructed objects but if
it is called as a function, then it is the responsibility of the call
implementation to do the job.

Comment 3

[Igor Bukanov]

I committed the fix

Comment 4

[Phil Schwartau]

Testcase added to JS testsuite:

      mozilla/js/tests/js1_5/Scope/regress-220584.js

Before Igor's fix, failed in Rhino exactly as described above.

Comment 5

[Igor Bukanov]

Trageting as resolved against 1.5R5