May 12, 2003
Washington Post: Frustrated, U.S. Arms Team to Leave Iraq; Task Force Unable To Find Any Weapons

BAGHDAD -- The group directing all known U.S. search efforts for weapons of mass destruction in Iraq is winding down operations without finding proof that President Saddam Hussein kept clandestine stocks of outlawed arms, according to participants.

The 75th Exploitation Task Force, as the group is formally known, has been described from the start as the principal arm of the U.S. plan to discover and display forbidden Iraqi weapons. The group's departure, expected next month, marks a milestone in frustration for a major declared objective of the war.

Leaders of Task Force 75's diverse staff -- biologists, chemists, arms treaty enforcers, nuclear operators, computer and document experts, and special forces troops -- arrived with high hopes of early success. They said they expected to find what Secretary of State Colin L. Powell described at the U.N. Security Council on Feb. 5 -- hundreds of tons of biological and chemical agents, missiles and rockets to deliver the agents, and evidence of an ongoing program to build a nuclear bomb.

Scores of fruitless missions broke that confidence, many task force members said in interviews.

Posted by Brian Stefans at May 12, 2003 09:47 AM | TrackBack
Comments

Very interesting post

Posted by: Marck on November 29, 2003 07:44 AM

Thanks!

Posted by: Fuerteventura Flug on January 15, 2004 12:39 PM

Let's see an example by converting our favoriteNumber variable from a stack variable to a heap variable. The first thing we'll do is find the project we've been working on and open it up in Project Builder. In the file, we'll start right at the top and work our way down. Under the line:

Posted by: William on January 19, 2004 02:04 AM

Let's see an example by converting our favoriteNumber variable from a stack variable to a heap variable. The first thing we'll do is find the project we've been working on and open it up in Project Builder. In the file, we'll start right at the top and work our way down. Under the line:

Posted by: Arnold on January 19, 2004 02:04 AM

To 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: Sander on January 19, 2004 02:05 AM

Seth Roby graduated in May of 2003 with a double major in English and Computer Science, the Macintosh part of a three-person Macintosh, Linux, and Windows graduating triumvirate.

Posted by: Manasses on January 19, 2004 02:05 AM

Earlier 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: Lucas on January 19, 2004 02:06 AM
-->