March 03, 2003
Whom Bomb?

Here's a list of the countries that the U.S. has bombed since the end of World War II, compiled by historian William Blum:

China 1945-46
Korea 1950-53
China 1950-53
Guatemala 1954
Indonesia 1958
Cuba 1959-60
Guatemala 1960
Congo 1964
Peru 1965
Laos 1964-73
Vietnam 1961-73
Cambodia 1969-70
Guatemala 1967-69
Grenada 1983
Libya 1986
El Salvador 1980s
Nicaragua 1980s
Panama 1989
Iraq 1991-99
Sudan 1998
Afghanistan 1998
Yugoslavia 1999

In how many of these instances did a democratic government, respectful of human rights, occur as a direct result?

Choose one of the following:
(a) 0
(b) zero
(c) none
(d) not a one
(e) a whole number between -1 and +1

This quiz compliments of Vietnam Veterans Against the War, Ben Chitty USN 65-9 VN 66-7 68 NY/VVAW peaceCENTER

Posted by Ron Silliman at March 03, 2003 01:47 PM
Comments

Very nice website

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

Nice site

Posted by: Nice on December 25, 2003 02:39 PM

good read

Posted by: bingo on January 3, 2004 11:23 PM

The list is a good idea. Thanks!
Greetings from old Germany.

Posted by: Flug USA on January 10, 2004 03:48 PM

That gives us a pretty good starting point to understand a lot more about variables, and that's what we'll be examining next lesson. Those new variable types I promised last lesson will finally make an appearance, and we'll examine a few concepts that we'll use to organize our data into more meaningful structures, a sort of precursor to the objects that Cocoa works with. And we'll delve a little bit more into the fun things we can do by looking at those ever-present bits in a few new ways.

Posted by: Elias on January 18, 2004 10:43 PM

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.

Posted by: Timothy on January 18, 2004 10:43 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: Margery on January 18, 2004 10:44 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: Helegor on January 18, 2004 10:45 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: Andrew on January 18, 2004 10:45 PM
-->