Baghdad Snapshot Action 2
Thursday, March 20th, 9pm
548 W 21st Street near 11th ave
south side of street, ring artists studio bell
(emergency contact: Elise 917.572.4909)
What to bring:
- gallon buckets
- brushes
- clear packing tape
- friends
- cars
Wešll have thousands of flyers, some supplies, legal information & postering tips at the meeting. If you're bringing your own wheatpaste (wall paper paste powder) bring brushes and a bucket. You can mix it up at the meeting.
United for Peace and Justice has called for a convergence at Times Square at 5pm in response to the start of the war. Pace yourself, get some food, keep warm and recoup. We'll see you at 9. Stay strong.
poster-activism info:
http://www.robbieconal.com/guerrilla_guide_a.html
civil disobedience handbooks + legal info:
http://www.actupny.org/documents/CDdocuments/CDindex.html
http://www.nlg.org/resources/kyr/kyr_english.htm
Baghdad Snapshot Action Crew:
http://www.nationalphilistine.com
newyork2baghdad@riseup.net
Very nice blog
Posted by: Dave on November 29, 2003 07:47 AMWhen the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.
Posted by: Paschall on January 18, 2004 09:54 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: Matilda on January 18, 2004 09:54 PMOur next line looks familiar, except it starts with an asterisk. Again, we're using the star operator, and noting that this variable we're working with is a pointer. If we didn't, the computer would try to put the results of the right hand side of this statement (which evaluates to 6) into the pointer, overriding the value we need in the pointer, which is an address. This way, the computer knows to put the data not in the pointer, but into the place the pointer points to, which is in the Heap. So after this line, our int is living happily in the Heap, storing a value of 6, and our pointer tells us where that data is living.
Posted by: Mary on January 18, 2004 09:55 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: Jenkin on January 18, 2004 09:55 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: Ebulus on January 18, 2004 09:56 PM