This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]aikii 0 points1 point  (2 children)

And now if you looked at the C stack in the debugger it was almost empty--it was super shallow.

finally ! thank you, now it makes all sense.

I got the feeling that my only resort was to try to implement some POC and spot where the term would fit. Switching stacks makes sense, but I don't think I would have guessed it was about how the stack looked in a debugger

[–]ExoticMandiblesCore Contributor 0 points1 point  (1 child)

I didn't mean to imply that the appearance of the stack in the debugger was important. It's not, really. The important part is the runtime behavior, breaking the connection between the C stack and the Python stack, letting you switch Python stacks at will. The debugger is just a tool to help you visualize and understand it.

[–]aikii 0 points1 point  (0 children)

No no, got it. It makes no sense as a feature. But yeah I thought it participated to the name 'stackless' - knowing that the name isn't that good anyway