Safely, again. We drove from Pittsburgh to Columbus, where we picked up our eldest child (back from Rochester for Christmas vacation), then rolled north enjoying three-part conversational harmony (with Nate’s choice of music) all the way to Chicago. He’s great, and we’re very proud of him.
My dad got up early to see us off. We had some coffee and orange juice, toast and eggs; he gave me some sage advice about starting a stretching regimen to improve my muscle tone; we took some pictures and hugged him and Susan goodbye. I hope he gets some rest between now and Wednesday, when my sister Holly arrives. Urge him as we might to take it easy, he was determined to spend a fair amount of time with us, and I’m sure it must be exhausting. Heavens, I was tired, and I hadn’t just had an abdominal aortic aneurysm (or three) repaired. We’ll keep Don and Susan in our prayers, and we thank you-all (I should say “youns,” since they’re in Pittsburgh) for your concern.
Posted by AKMA at December 21, 2003 09:00 PM | TrackBackThese secret identities serve a variety of purposes, and they help us to understand how variables work. In this lesson, we'll be writing a little less code than we've done in previous articles, but we'll be taking a detailed look at how variables live and work.
Posted by: Julius at January 12, 2004 09:13 PMEach 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: Wombell at January 12, 2004 09:14 PMEarlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.
Posted by: Godfrey at January 12, 2004 09:14 PMThe most basic duality that exists with variables is how the programmer sees them in a totally different way than the computer does. When you're typing away in Project Builder, your variables are normal words smashed together, like software titles from the 80s. You deal with them on this level, moving them around and passing them back and forth.
Posted by: Rook at January 13, 2004 10:29 AMA 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: Adrian at January 13, 2004 10:30 AMFor this program, it was a bit of overkill. It's a lot of overkill, actually. There's usually no need to store integers in the Heap, unless you're making a whole lot of them. But even in this simpler form, it gives us a little bit more flexibility than we had before, in that we can create and destroy variables as we need, without having to worry about the Stack. It also demonstrates a new variable type, the pointer, which you will use extensively throughout your programming. And it is a pattern that is ubiquitous in Cocoa, so it is a pattern you will need to understand, even though Cocoa makes it much more transparent than it is here.
Posted by: Cecily at January 13, 2004 10:30 AM