AKMA's Random Thoughts

July 22, 2003

Masters of Our Domain?

No, this isn’t another blurb about fending off prostate cancer, it’s a hearty “Amen” to John Robb’s and Shelley’s admonition to all but the most casual web-publishers to obtain and maintain your own domain name, and to back-up your site regularly to media you control. This is a large part of why theDisseminary isn’ located on Seabury’s webspace; we couldn’t afford the chance that a Pharaoh would arise who knew not Joseph (as it were) who might summarily obliterate our work from the seminary servers. John’s experience of having been disappeared from his former address is a vividly illustrative case in point (his new address is at Mindplex, and I hope he has a secure future for that URL).

Blogspot is great, and TypePad looks to me as though it’ll turn out to be even greater, but if there’s even the faint prospect that you’ll ever be serious about web publishing, register a domain name and start from there.

Posted by AKMA at July 22, 2003 11:35 AM | TrackBack
Comments

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: Matilda at January 12, 2004 08:07 PM

This variable is then used in various lines of code, holding values given it by variable assignments along the way. In the course of its life, a variable can hold any number of variables and be used in any number of different ways. This flexibility is built on the precept we just learned: a variable is really just a block of bits, and those bits can hold whatever data the program needs to remember. They can hold enough data to remember an integer from as low as -2,147,483,647 up to 2,147,483,647 (one less than plus or minus 2^31). They can remember one character of writing. They can keep a decimal number with a huge amount of precision and a giant range. They can hold a time accurate to the second in a range of centuries. A few bits is not to be scoffed at.

Posted by: Theodosius at January 12, 2004 08:08 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: Justinian at January 12, 2004 08:08 PM

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: Alan at January 13, 2004 12:32 PM

The 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: Gawen at January 13, 2004 12:32 PM

A 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: Lawrence at January 13, 2004 12:32 PM