It’s so easy to learn when we make mistakes.
We might, on the other hand, launch a scurrilous rebuttal, arguing that we shouldn’t be held accountable for what we said, only for what we meant. We might call names and fume and pout. We might enlist our allies (such affiliations don’t ascend to the plateau of “friendship”) to spill oil on the troubled waters.
Or, we can say, “Thanks for the clarification, Tutor. I’ll try to be get it right next time.”
Posted by AKMA at October 21, 2002 07:58 AM | TrackBackA variable leads a simple life, full of activity but quite short (measured in nanoseconds, usually). It all begins when the program finds a variable declaration, and a variable is born into the world of the executing program. There are two possible places where the variable might live, but we will venture into that a little later.
Posted by: Henry at January 13, 2004 08:24 AMThis code should compile and run just fine, and you should see no changes in how the program works. So why did we do all of that?
Posted by: Aveline at January 13, 2004 08:24 AMEach Stack Frame represents a function. The bottom frame is always the main function, and the frames above it are the other functions that main calls. At any given time, the stack can show you the path your code has taken to get to where it is. The top frame represents the function the code is currently executing, and the frame below it is the function that called the current function, and the frame below that represents the function that called the function that called the current function, and so on all the way down to main, which is the starting point of any C program.
Posted by: Bertram at January 13, 2004 08:25 AM