-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: 9
-
Component/s: core-libs
-
None
-
b70
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8098779 | emb-9 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | team |
| JDK-8129212 | 8u65 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | b02 |
| JDK-8087332 | 8u60 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | b20 |
| JDK-8138547 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b02 |
| JDK-8129737 | emb-8u60 | Sundararajan Athijegannathan | P4 | Resolved | Fixed | b20 |
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.
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.
- backported by
-
JDK-8087332 Indirect evals should be strict with -strict option
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-