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

Deprecate the CONTEXT function #2123

Open
rebolbot opened this issue Mar 5, 2014 · 3 comments
Open

Deprecate the CONTEXT function #2123

rebolbot opened this issue Mar 5, 2014 · 3 comments

Comments

@rebolbot
Copy link
Collaborator

rebolbot commented Mar 5, 2014

Submitted by: BrianH

Rebol is a language with context-sensitive semantics - we call it "dialects". When explaining Rebol's semantics to people with any kind of CS background or who somehow otherwise know what "context-sensitive" means, that is the term that works best for getting the ideas across, to explain what the term "dialect" means.

This fails completely when we start using the term "context" to refer to an object, because it's not a term that anyone else uses for this, and it's hard to explain why we're using it. Normally, we'd just prefer to use other terms for this, but it's difficult when we have a function named CONTEXT that (inexplicably) just generates an object. Going forward, we'll be better off calling the function OBJECT (#2118) and never mentioning CONTEXT again.

With #2118, this is just a matter of adding a value alias for the new OBJECT named CONTEXT, and putting in a comment saying it's deprecated. That will give us time to get rid of references to the CONTEXT function.

CC - Data [ Version: r3 master Type: Wish Platform: All Category: Mezzanine Reproduce: Always Fixed-in:none ]

@rebolbot
Copy link
Collaborator Author

rebolbot commented Mar 7, 2014

Submitted by: BrianH

Finalizing the name of #2119 and refining #2118 makes it possible to deprecate CONTEXT more slowly. Severity adjusted accordingly.

@rebolbot
Copy link
Collaborator Author

rebolbot commented Mar 7, 2014

Submitted by: Ladislav

I adjusted severity to major since it would require changes and revisions of existing code.

@rebolbot
Copy link
Collaborator Author

rebolbot commented Mar 7, 2014

Submitted by: BrianH

OK, though "require changes and revisions of existing code" is not a blocker here. This is a #666 issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant