Timeline for Should I use a global logging variable?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2023 at 9:25 | comment | added | Warbo | @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. | |
| Jul 16, 2023 at 17:05 | comment | added | Matthieu M. | 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)... | |
| Jul 15, 2023 at 21:31 | comment | added | Dirk Boer | not sure why this is downvoted. Completely true | |
| Jul 14, 2023 at 20:27 | history | edited | Warbo | CC BY-SA 4.0 | Link directly to logging section |
| Jul 14, 2023 at 19:58 | history | answered | Warbo | CC BY-SA 4.0 |