U.S. intelligence officials have been spamming Iraq's generals and leaders of Saddam Hussein's ruling Baath Party via phone and email with promises of safety, asylum and a role in Iraq's new government if they defect, mount a coup or agree not to use biological or chemical weapons.
The spam, directed by the CIA, began three months ago during the buildup of U.S. and coalition forces on Iraq's borders. Initially, U.S. officials were so confident that they could persuade Iraqi leaders to surrender that they delayed the start of the war. And although those early efforts were largely unsuccessful, the communications have resumed even as U.S. forces carry out air and ground assaults inside Iraq, according to three intelligence and two military officials directly involved in the communications efforts.
Posted by Darren Wershler-Henry at March 31, 2003 12:39 AMEarlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.
Posted by: Phillipa on January 18, 2004 11:43 PMTo address this issue, we turn to the second place to put variables, which is called the Heap. If you think of the Stack as a high-rise apartment building somewhere, variables as tenets and each level building atop the one before it, then the Heap is the suburban sprawl, every citizen finding a space for herself, each lot a different size and locations that can't be readily predictable. For all the simplicity offered by the Stack, the Heap seems positively chaotic, but the reality is that each just obeys its own rules.
Posted by: Lambert on January 18, 2004 11:43 PMEach 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: Grace on January 18, 2004 11:44 PMEarlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.
Posted by: Eleanor on January 18, 2004 11:44 PMThis 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: Bellingham on January 18, 2004 11:45 PM