In what can only be construed as the gravest of lapses in judgment, Dean Allen seems to have bought Blogshares in my humble publication. Compounding the folly of that investment, though, he has bought into the blog at my former address, which I expect will not appreciate in value (although what I know about anything even vaguely resembling financial markets is easily surpassed by what Margaret knows about cricket).
In the course of exploring this otherwise inexplicable phenomenon, I discovered that this very blog has a separate Blogshares ownership and valuation. Moreover, whereas the past blog had a middlin’ kind of value, it looks as though the Disseminary blog is rather expensive. So I reckon that Dean ought to get out of the dead-end Seabury shares and invest in Disseminary shares, if he can. Heck, I’d give him some if I had any myself, which I don’t think I do.
Of course, one result of all this is that — Allen being a moralist of the strictest sort — now he would never ever mention me in his blog, since that would affect the price of shares he owns. There’s no particular reason for him to refer to goings-on here in the first instance (I’m at something of a loss to figure why he bought in; maybe the shares were a joke birthday present, the online equivalent of a Talking Bass); theology, metablogging, and my family aren’t topics that typically engage his interest. (If he wanted to donate some design services to the Disseminary, though, we’d ecstatically accept the offer.) But the SEC of Blogshares would probably extradite him from Pompignac straight back to Toronto if he added to the value of his investment by using his influential site to leverage my status upward. So, one more prominent blogger guaranteed not to link here.
Posted by AKMA at July 19, 2003 11:09 PM | TrackBackA HA! He knows a collector's edition when he sees it!
Posted by: jeneane at July 22, 2003 01:32 AMBut variables get one benefit people do not
Posted by: Edwin at January 13, 2004 12:25 PMInside 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: John at January 13, 2004 12:25 PMThis 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: Samuel at January 13, 2004 12:25 PM