AKMA's Random Thoughts

March 25, 2003

Viral

When I re-jigger my blogroll — which I actually will, someday, soon — I’ll have a section called “Blogeny” for kids-o’bloggers, now including not only Si-man but also Jane’s daughter CJ and Chris’s daughter Selene.

[Kevin reminds me that I left out Andrew Marks — corrected!]

Have you noticed that I’m having a blast using NetNewsWire?

DRMA: "Porcelain" by Moby; "Flight 19" by Phil Manzanera and 801.

Posted by AKMA at March 25, 2003 04:26 PM | TrackBack
Comments

...and not to forget Elaine and her son.

/m

Posted by: Michael at March 25, 2003 08:54 PM

This will allow us to use a few functions we didn't have access to before. These lines are still a mystery for now, but we'll explain them soon. Now we'll start working within the main function, where favoriteNumber is declared and used. The first thing we need to do is change how we declare the variable. Instead of

Posted by: Machutus at January 13, 2004 10:22 AM

When compared to the Stack, the Heap is a simple thing to understand. All the memory that's left over is "in the Heap" (excepting some special cases and some reserve). There is little structure, but in return for this freedom of movement you must create and destroy any boundaries you need. And it is always possible that the heap might simply not have enough space for you.

Posted by: Laura at January 13, 2004 10:23 AM

Inside each stack frame is a slew of useful information. It tells the computer what code is currently executing, where to go next, where to go in the case a return statement is found, and a whole lot of other things that are incredible useful to the computer, but not very useful to you most of the time. One of the things that is useful to you is the part of the frame that keeps track of all the variables you're using. So the first place for a variable to live is on the Stack. This is a very nice place to live, in that all the creation and destruction of space is handled for you as Stack Frames are created and destroyed. You seldom have to worry about making space for the variables on the stack. The only problem is that the variables here only live as long as the stack frame does, which is to say the length of the function those variables are declared in. This is often a fine situation, but when you need to store information for longer than a single function, you are instantly out of luck.

Posted by: Denton at January 13, 2004 10:23 AM