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

Global environment in the specification #7

Open
38a938c2 opened this issue Apr 6, 2019 · 0 comments
Open

Global environment in the specification #7

38a938c2 opened this issue Apr 6, 2019 · 0 comments

Comments

@38a938c2
Copy link

38a938c2 commented Apr 6, 2019

As the reference implementation defines global-environment to extract a global environment corresponding to the lexical environment, and this is an implicit assumption in the specification, add some explicit mentions of that into the specification.

Apparently global environment is expected to support the same protocol as the lexical environment (and more than that); not sure about the global-environment request itself. (Should the property of being global determined by global-environment returning the same object? Nil? By a special predicate? By being a subclass of a specified class?)

Probably also mention that the expected behaviour of «language processor» third-party libraries is to query a lexical environment, and fall back to explicitly querying the corresponding global environment in case of failure.

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

No branches or pull requests

1 participant