« Bugzilla Issues Index
#3301 — Globals not treated as var bindings
- bug_id:
3301
- creation_ts:
2014-10-28 09:46:00 -0700
- short_desc:
Globals not treated as var bindings
- delta_ts:
2014-12-07 14:35:09 -0800
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 23: April 5, 2014 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
enhancement
- everconfirmed:
true
- reporter:
Andreas Rossberg
- assigned_to:
Allen Wirfs-Brock
- commentid:
10541
- comment_count:
0
- who:
Andreas Rossberg
- bug_when:
2014-10-28 09:46:41 -0700
The VarNames list of the global env is currently created empty. It should initially contain all global names defined in Sec. 18, so that code like the following is not allowed.
<>
function f(x) { return x === undefined }
</>
<>
let undefined = 666
</>
- commentid:
10711
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2014-12-03 15:50:37 -0800
At the Nov. TC39 meeting we decide to forbind global lexical declarations that would shadow non-configurable own properties of the global object. This takes care of bui;t-ins like undefined and infinity.
Apply this to Ch 18 names would be future hostile as it essentially means that any future addition to the chapter 18 names would be a breaking change.
fixed in rev29 editor's draft
- commentid:
10925
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2014-12-07 14:35:09 -0800
fixed in rev29