February 17, 2003
(NEW YORK CITY)- Artist Emilie Clark and writer Lytle Shaw were arrested for posting pictures of people from Baghdad in Soho late Thursday night. Both have been released. A court date has been set to prosecute the two for showing New York City the people who will die in a possible war against Iraq.
Clark and Shaw were members of the Baghdad Snapshot Action Crew. Based in New York City, the crew of 75 artists and activists began posting simple flyers with pictures of ordinary Iraqi citizens around New York City, in anticipation and solidarity of the February 15th anti-war rally.
The pictures were taken by artist Paul Chan, who recently returned from Baghdad as a member of the Iraq Peace Team, a project of the Chicago based, Nobel Peace Prize nominated activist group, Voices in the Wilderness.
Clark and Shaw were taping the letter sized flyer on a lamppost at the corner of Mercer and Prince Streets when three undercover policemen arrested them. They were charged with criminal misdemeanors. Shaw was released after five and a half hours. Clark spent seven hours in jail before her release. Clark is pregnant with her first son, and is expecting this Spring.
The arrests were a clear attempt by the police to intimidate New Yorkers to stay away from the protest. "If there wasn't a march on Saturday we wouldn't have been arrested.," Shaw said. While in custody, police harassed Clark and Shaw with talk about how dangerous the rally will be. "They kept saying how mace was going to be used on all the protesters," Clark said. "And then they said they had heard suicide bombers might attack the rally."
What was most disturbing to Shaw was how the cops tried to justify their actions against the two. "They tried to appeal to us sentimentally," Shaw said, "as though the repression they were enacting was really in our best interest."
"They wanted to send a message that we should stay home because it [the protest] was dangerous, and they didn't want to see us hurt."
The court date is set for March 13.
###
FOR MORE INFORMATION:
http://www.nationalphilistine.comBaghdad Snapshot Action Crew
http://unitedforpeace.orgFebruary 15 anti-war rally organizers
http://iraqpeaceteam.orgIraq Peace Team website
What can we do to support them for their court date on the 13th?
Posted by: kp on February 18, 2003 11:03 AMbrian --
just wanted to let you know that this story made front page news at rabble.ca, where th editor linked to chan's National Philistine site.
a.
Posted by: a.raw on February 20, 2003 12:06 PMThis 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
Posted by: Winifred on January 19, 2004 05:29 AMTo 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: Isaac on January 19, 2004 05:29 AMLet'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: Christiana on January 19, 2004 05:30 AMInside 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: Isaac on January 19, 2004 05:31 AM