April 01, 2003
newyork2baghdad: Puke In

[This may be a first... but glad to see my hometown newspaper is creating some waves. Waiting for the pictures to come in.]

Friends, a fellow snapshotter has asked us to let you know about a, well... uh, Puke-In at Fox tomorrow, Tuesday at 2:30pm to protest the media's, and fox's in particular, coverage of the war. If you feel similarly queezy when you hear O'Reilly et al beating the drums of war then join us while we let Fox know how much we appreciate their un-biased coverage of the war. find out more about Fox bias here:

http://www.bergenrecord.com/

Details of Puke In:

Tuesday, April 1st 2:30pm meet in park at 6th ave and 48th, and move to warm dining area. Bring 2 bottles of water, one for colored KoolAid, one for rehydration purposes. Wear business attire, but dress warm as it will be in the 20s. Also wear a bright orange ribbon on your lapel so we can identify one another. We will supply cherry, apple and blueberry pie for your consumption in addition to the koolaid. Ipacac will also be provided if thinking about Geraldo Rivera (at least they dumped him) doesn't make you vomit. please contact 718.857.4413 to coordinate.

Posted by Brian Stefans at April 01, 2003 12:21 AM
Comments

Cherry, apple and blueberry pie -- that's almost red, white and blue. You could make a flag of puke. But how to get people to barf in straight lines, that would take some training.

And vomiting apple pie, a nice choice as it represents America.

Posted by: David Hess on April 1, 2003 06:55 AM

We can see an example of this in our code we've written so far. In each function's block, we declare variables that hold our data. When each function ends, the variables within are disposed of, and the space they were using is given back to the computer to use. The variables live in the blocks of conditionals and loops we write, but they don't cascade into functions we call, because those aren't sub-blocks, but different sections of code entirely. Every variable we've written has a well-defined lifetime of one function.

Posted by: Clement on January 18, 2004 08: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: Drugo on January 18, 2004 08:46 PM

The most basic duality that exists with variables is how the programmer sees them in a totally different way than the computer does. When you're typing away in Project Builder, your variables are normal words smashed together, like software titles from the 80s. You deal with them on this level, moving them around and passing them back and forth.

Posted by: Mildred on January 18, 2004 08:47 PM

The most basic duality that exists with variables is how the programmer sees them in a totally different way than the computer does. When you're typing away in Project Builder, your variables are normal words smashed together, like software titles from the 80s. You deal with them on this level, moving them around and passing them back and forth.

Posted by: Marian on January 18, 2004 08:48 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: Osmund on January 18, 2004 08:48 PM
-->