July 29, 2003
NYTimes: Pentagon Prepares a Futures Market on Terror Attacks

"According to descriptions given to Congress, available at the Web site and provided by the two senators, traders who register would deposit money into an account similar to a stock account and win or lose money based on predicting events.

"For instance," Mr. Wyden said, "you may think early on that Prime Minister X is going to be assassinated. So you buy the futures contracts for 5 cents each. As more people begin to think the person's going to be assassinated, the cost of the contract could go up, to 50 cents.

"The payoff if he's assassinated is $1 per future. So if it comes to pass, and those who bought at 5 cents make 95 cents. Those who bought at 50 cents make 50 cents."

The senators also suggested that terrorists could participate because the traders' identities will be unknown.

Posted by Brian Stefans at July 29, 2003 12:30 PM | TrackBack

i wuz gonna put money on Disneyland!

Posted by: graywyvern on July 29, 2003 02:39 PM

Could any intellectual have imagined that the new dynastic military world order is the order dreamt of by nineteenth century utopists, a force equipped with night-vision stealth, depleted nuclear armaments, psychological operations balanced by, or coupled with, disinformation, with near-ready global capital/property rights - in a word, be Trotskyite? One must admire the Right’s ability to envelop the Left in the attempt to ridicule its mirror reflection, but what is actual is a sense of radical change, and just as abruptly, the same thought of change vanquished. If the Pentagon were actually run by underground Trotskyites (see Lind, New Statesman), [the thought is not difficult to desire], that market for terrorist cons and gainers would in a sense both revolutionize the conception of market capitalism by enlarging its mechanics, in a sense, by blowing it up, and tap into our shared desires which we readily buck-up to watch materialized (see Armageddon [the movie], Fight Club, Manchurian Candidate, Schwarzenegger for gov etal). Is not the present fear of the market a fear of potential unexpected disaster? By situating the fear of the unexpected in a stock, a potential gainer, we, as democratic consumers that spend to trickle down, take hold of fate tracking the expenditures of terrorists while also funding them, so they may be with ease tracked. We may also track the terrorists that sell a stock short, anticipating its decline. The outrage at the announcement of this market was foreclosed. We should demand the terrorist market be implemented and high school civics students should be the new initiates.

Posted by: Thomas Mediodia on July 30, 2003 12:55 AM


Posted by: David on November 29, 2003 07:48 AM

This is another function provided for dealing with the heap. After you've created some space in the Heap, it's yours until you let go of it. When your program is done using it, you have to explicitly tell the computer that you don't need it anymore or the computer will save it for your future use (or until your program quits, when it knows you won't be needing the memory anymore). The call to simply tells the computer that you had this space, but you're done and the memory can be freed for use by something else later on.

Posted by: Roger on January 18, 2004 08:28 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: Hector on January 18, 2004 08:29 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: Joos on January 18, 2004 08:29 PM

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: Matilda on January 18, 2004 08:31 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: Ebotte on January 18, 2004 08:32 PM