Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[normative] Limit application of Annex B extension #460

Closed

Conversation

jugglinmike
Copy link
Contributor

Ensure that legacy extensions to GlobalDeclarationInstantiation are only
observed when the script source is not strict mode code.

Ensure that legacy extensions to GlobalDeclarationInstantiation are only
observed when the script source is not strict mode code.
@erights
Copy link

erights commented Mar 6, 2016

What legacy extensions are you referring to? What Annex B text are you referring to? I didn't find anything when searching http://www.ecma-international.org/ecma-262/6.0/ for GlobalDeclarationInstantiation. The only uses I found of this name are in section 15.1.

@jugglinmike
Copy link
Contributor Author

This is a patch for the 2016 revision of the specification, so you'll want to reference that document:

https://tc39.github.io/ecma262/2016/#sec-block-level-function-declarations-web-legacy-compatibility-semantics

@erights
Copy link

erights commented Mar 6, 2016

Yes, this seems like a necessary change. Thanks!

@jugglinmike
Copy link
Contributor Author

Figures: I only added two lines and managed to get a typo into one of them. Thanks for the review!

@littledan
Copy link
Member

LGTM, and this'd better be backported to the 2016 draft, right @bterlson?

bterlson pushed a commit that referenced this pull request Mar 25, 2016
Ensure that legacy extensions to GlobalDeclarationInstantiation are only
observed when the script source is not strict mode code.

Fixes #460.
@bterlson bterlson closed this in 488b482 Mar 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants