August 04, 2003

Wired News: Bush Impeached? Wanna Bet?

Wired News: Bush Impeached? Wanna Bet?

stripped_dryerase.jpg

Though there was an outcry over the Pentagon's terrorism futures market, a similar online exchange is in the works to predict what the U.S. government is up to.

The American Action Market will offer various Washington "futures" that can be bet upon and traded. Examples include:

•Which country will the White House threaten next?

•Who will be the next foreign leader to move off the CIA payroll and onto the White House's "most wanted" list?

•Which corporation with close ties to the White House will be the next cloaked in scandal?

The AAM will begin registering traders in September and plans to open for business Oct. 1 -- the same launch date proposed for the Pentagon's terrorism market, until it was shelved.

Posted by Brian Stefans at August 4, 2003 12:07 PM | TrackBack
Comments

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: Silvester at January 18, 2004 09:09 PM

Our next line looks familiar, except it starts with an asterisk. Again, we're using the star operator, and noting that this variable we're working with is a pointer. If we didn't, the computer would try to put the results of the right hand side of this statement (which evaluates to 6) into the pointer, overriding the value we need in the pointer, which is an address. This way, the computer knows to put the data not in the pointer, but into the place the pointer points to, which is in the Heap. So after this line, our int is living happily in the Heap, storing a value of 6, and our pointer tells us where that data is living.

Posted by: Margaret at January 18, 2004 09:09 PM

When 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: Godfrey at January 18, 2004 09:09 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: Anthony at January 18, 2004 09:10 PM

These 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: Rosanna at January 18, 2004 09:10 PM