I don't think your stack definition is quite right... you more described debugging.
A stack in general is no different than a stack of papers: you can see and access what's on top, but if you want something on the bottom, you first have to take off what's on top.
"The" stack (as in stack trace) is a particular stack recording how code got to the current line being executed (foo called bar called baz called fizz called buzz and on down the line)
Even so, a call stack isn't an action. I agree that the definition is a bit off. When someone is debugging code, they will interact with the stack. But the stack itself isn't the act of debugging.
Ooo, this is very helpful. I've been grappling with how exactly to explain stack. I certainly explained "stack" here as what is actually a "call stack". Thank you for the input!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't think your
stackdefinition is quite right... you more described debugging.A stack in general is no different than a stack of papers: you can see and access what's on top, but if you want something on the bottom, you first have to take off what's on top.
"The" stack (as in stack trace) is a particular stack recording how code got to the current line being executed (foo called bar called baz called fizz called buzz and on down the line)
I would say she meant the 'call stack'
Exactly so. Thank you!
Even so, a call stack isn't an action. I agree that the definition is a bit off. When someone is debugging code, they will interact with the stack. But the stack itself isn't the act of debugging.
Ooo, this is very helpful. I've been grappling with how exactly to explain stack. I certainly explained "stack" here as what is actually a "call stack". Thank you for the input!