Phase One-and-a-Half of the Great Disseminary migration has begun and, mostly, concluded satisfactorily. With much hand-holding from Dorothea and Michal, I got Moveable Type installed. I did, however, screw up a number of things along the way, so it’ll take a little more hand-holding, along with perhaps some anesthesia and furniture repair, actually to get Moveable Type working.
It’s one step closer to Trevor’s and my plan for world domination <evil chuckle=. . . .
Posted by AKMA at March 26, 2003 11:02 PM | TrackBackumm...somehow I am not afraid. I guess you could pacify us to death.
Posted by: Tripp at March 27, 2003 08:11 AMLet's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.
Posted by: Gregory at January 12, 2004 10:58 PMThe Stack is just what it sounds like: a tower of things that starts at the bottom and builds upward as it goes. In our case, the things in the stack are called "Stack Frames" or just "frames". We start with one stack frame at the very bottom, and we build up from there.
Posted by: Ottewell at January 12, 2004 10:59 PMLet's see an example by converting our favoriteNumber variable from a stack variable to a heap variable. The first thing we'll do is find the project we've been working on and open it up in Project Builder. In the file, we'll start right at the top and work our way down. Under the line:
Posted by: Andrew at January 12, 2004 10:59 PMThese 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: Geoffrey at January 13, 2004 10:24 AMWhen the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.
Posted by: Jeremy at January 13, 2004 10:25 AMWhen a variable is finished with it's work, it does not go into retirement, and it is never mentioned again. Variables simply cease to exist, and the thirty-two bits of data that they held is released, so that some other variable may later use them.
Posted by: Roland at January 13, 2004 10:25 AM