GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||
GeezerVison is showing github.com — gh-119786: move frames documentation to InternalDocs and add details by iritkatriel · Pull Request #121009 · python/cpython Conversation
|
|
|
||
| * Local variables (including arguments, cells and free variables) | ||
| * Evaluation stack | ||
| * Evaluation stack and instruction pointer |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I don't think the instruction pointer belongs here (at least not conceptually).
I would add it to specials/linkage
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
How about I change this line to
Execution state: evaluation stack, instruction pointer ?
It feels like instruction pointer is internal to the frame's working, rather than linking to external frames or objects.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
I think it would make sense to merge the "specials" and "linkage" sections. The only real "linkage" is the So, maybe replace "specials and linkage" with "specials", and when specifically referring to "linkage", say |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.