JDK-8087211 : Indirect evals should be strict with -strict option
- Type: Bug
- Component: core-libs
- Sub-Component: jdk.nashorn
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-06-11
- Updated: 2015-09-29
- Resolved: 2015-06-12
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u60Fixed  |
9 b70Fixed |
Description
When -strict option, all evals regardless of "direct" or "indirect" have to be strict. This rule is consistent with Rhino.
With nashorn, all Functions are strict with -strict flag. But indirect evals are not strict with -strict.
Test script:
// indirect eval. Undefined variable assignment
this.eval("x = 44");
The above should result in ReferenceError with -strict option.