Originally at 2015-01-18T15:46:07Z by Herbert Vojčík
Packages are compiled into big closures (from 0.11) used as AMD factories (from 0.12). There closures contain some local variables / AMD callback parameters that are defined globally for every method in package.
ASTInterpreter should take this into account when interpreting code (it should be able to get this context via #1135).
Originally at 2015-01-18T15:46:07Z by Herbert Vojčík
Packages are compiled into big closures (from 0.11) used as AMD factories (from 0.12). There closures contain some local variables / AMD callback parameters that are defined globally for every method in package.
`ASTInterpreter` should take this into account when interpreting code (it should be able to get this context via #1135).
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7851752-astinterpreter-should-use-globals-from-local-context-of-a-package?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github).
</bountysource-plugin>
Originally at 2015-01-18T15:46:07Z by Herbert Vojčík
Packages are compiled into big closures (from 0.11) used as AMD factories (from 0.12). There closures contain some local variables / AMD callback parameters that are defined globally for every method in package.
ASTInterpreter
should take this into account when interpreting code (it should be able to get this context via #1135).Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.