Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

not sure why this is downvoted. Completely true

Dirk Boer
– Dirk Boer

2023-07-15 21:31:08 +00:00
Commented Jul 15, 2023 at 21:31
2

The most efficient way to implement dynamic scoping is NOT to walk up the stack, but instead to have a "global" stack (for each dynamic thingy) for which the top can be consulted in O(1)...

Matthieu M.
– Matthieu M.

2023-07-16 17:05:22 +00:00
Commented Jul 16, 2023 at 17:05
@MatthieuM. sure, as an implementation detail (although it gets tricky with concurrency). I don't like that as a mental model though, since it relies on semantics of mutability, time, etc. which we may not want/have in our surface language: e.g. dynamic scope works perfectly well in a pure-functional setting, pushing/popping a stack in-place has no meaning.

Warbo
– Warbo

2023-07-17 09:25:20 +00:00
Commented Jul 17, 2023 at 9:25

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »