April 28, 2003
whitehouse.org: The War In Iraq Concluded, President Bush Proudly Honors The First-Ever Recipients Of The "Civilian Warmonger Medal Of Armchair Valor"
THE PRESIDENT: Good afternoon. Welcome to the first-ever awards ceremony for the "Civilian Warmonger Medals of Armchair Valor" (view medal). I can't tell you how gonzo happy I am to personally honor these famous folks, each of whom so bravely absorbed the combat from the terrifying vantagepoint of overstuffed La-Z-Boys, feverishly pumping their crotch triggers in time to the thumping score of FOX NEWS warnography, then obediently chastising anyone who dared voice opinions that weren't in my fucking script!
Before we get to the goods though, I want to thank our corporate sponsors for providing us with this little banquet. So let's give a Texas-sized shout-out to the good folks at Pepsico's Taco Bell division! (Applause.) I'll tell you, nothing says "Mexcellence" to me like the all-new "JDAM Gordita Supreme" - guaranteed to deliver a precision-guided payload of cheez-drenched Camel Asada straight to your clammy, dimpled American ass.
And now, without further AH-DOOOO – the coveted "Civilian Warmonger Medals of Armchair Valor" go to the following fearless, two-faced Americans...
Posted by Brian Stefans at April 28, 2003 04:15 PM
If you don't like this site, go to the other million sites that applaud YOUR side of the story.
Let us choose what we want to read. Lucky for us there are people like Mr. Arras that make our searches easier.
Thanks Brian. Keep up the good work.
Yes, a good site. Thanks!
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.
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
Note first that favoriteNumbers type changed. Instead of our familiar int, we're now using int*. The asterisk here is an operator, which is often called the "star operator". You will remember that we also use an asterisk as a sign for multiplication. The positioning of the asterisk changes its meaning. This operator effectively means "this is a pointer". Here it says that favoriteNumber will be not an int but a pointer to an int. And instead of simply going on to say what we're putting in that int, we have to take an extra step and create the space, which is what does. This function takes an argument that specifies how much space you need and then returns a pointer to that space. We've passed it the result of another function, , which we pass int, a type. In reality, is a macro, but for now we don't have to care: all we need to know is that it tells us the size of whatever we gave it, in this case an int. So when is done, it gives us an address in the heap where we can put an integer. It is important to remember that the data is stored in the heap, while the address of that data is stored in a pointer on the stack.
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.
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.