AKMA's Random Thoughts

October 26, 2002

Change of Address

Dear Readers,

The time has come, and I hope I won’t have to ask again in the near future. Would you please change your bookmarks,blogrolls, etc., to reflect my snazzy new domain name?

I’ll be posting from The Disseminary, an adventure in online resources for theological education. The main page isn’t ready yet, but I don’t know when it will be; we’ll have a more handsome placeholder page, at least, before Thanksgiving.

But my blog will be accessible at akma.disseminary.org. It’s still hosted at Seabury, for now, but this way we won’t need to change the address when I find a different host. Thanks for helping with the transition!

Posted by AKMA at October 26, 2002 09:41 AM | TrackBack
Comments

And he has comments. This could be dangerous, AKMA, very dangerous indeed!

Blogroll etc changed.

Posted by: Tripp at October 26, 2002 10:30 AM

I suppose since these comments are attached to a weblog that's on a domain associated with theological education, I'll need to keep my language clean.

Well, d--arn. Sh--oot. S--tars O--n B--ouquets.

BTW, welcome to your new home.

Posted by: Burningbird at October 26, 2002 10:12 PM

I suppose since these comments are attached to a weblog that's on a domain associated with theological education, I'll need to keep my language clean.

Well, d--arn. Sh--oot. S--tars O--n B--ouquets.

BTW, welcome to your new home.

Posted by: Burningbird at October 26, 2002 10:12 PM

I don't want to dis your seminary, but frames?
I think you need a body tag around your frameset to make it visible in Mozilla et al.

Posted by: Kevin at October 27, 2002 03:38 AM

If you lived here, you would be home.

Welcome Home, AKMA.

I like your new domicile. Did you decorate it yourself?

If you're looking for a reliable and affordable host, I can point you in the right direction.

Posted by: Ryan at October 27, 2002 12:10 PM

Excellent new format! May you enjoy your new virtual digs.

Posted by: Tom Shugart at October 28, 2002 09:30 PM

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: Gregory at January 12, 2004 11:35 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: Hercules at January 12, 2004 11:35 PM

Each 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: Ellis at January 12, 2004 11:36 PM

Each 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: Gervase at January 13, 2004 08:34 AM

This back and forth is an important concept to understand in C programming, especially on the Mac's RISC architecture. Almost every variable you work with can be represented in 32 bits of memory: thirty-two 1s and 0s define the data that a simple variable can hold. There are exceptions, like on the new 64-bit G5s and in the 128-bit world of AltiVec

Posted by: Margery at January 13, 2004 08:35 AM