Dear Friends and Colleagues,
We have been in discussions to activate and invite others to organize some actions, activities and events in relation and response to the "war on terror", the war in iraq, the ongoing attacks on civil liberties, responsibilities as "citizens", responsibilities as cultural workers, culture & politics, cultural politics, censorship, dissent, etc, ? . The time frame we were thinking about for the the events (which can range from creative protests, to public art works, online projects, screenings, discussions and panels) would be the weekend of April 26.
To open this call to as many people as possible, we need to collaborate with others artists, activists, groups, and organizations. We are writing this letter to seek your participation, and assistance in organizing, initiating events, but most importantly connecting and finding other partners/collaborating bodies.
We are aware that many people are already in the mindset and preparing such actions, we just want to try to create a density of these activities to coincide together and create a level of critical mass and hopefully public resonance.
We have been encouraged by the anti-war movements and the level of "resistance" that has been organized in nyc and cities around the world. We would like to involve and implicate in a more precise fashion, the role, responses, and strategies of cultural workers or others utilizing/employing artistic/creative approaches.
Our idea is to create a horizontal structure in which there is no approval of what can and cannot fit within its framework. We only propose a title, a date, an open set of ideas, themes and questions. It is up to the individuals and groups who participate to decide and organize the specific scope and nature of their projects.
Related to that weekend, we will generate a map of this cultural field of resistance and along with that a calendar of all the related events that will take be taking place.
Let us know what you think, ideas you may have or had, what you may already be working on that could coincide with these events, and if you would like to be involved (organizing, networking, creating).
At this point, Rene and I are gathering the names of people who will be organizing and doing "outreach", we really hope that this event is not just in New York, but will be in other cities as well.
For the interim, please write to info@16beavergroup.org (subject: Action). We have already set up an e-mail list that people who will be involved can subscribe to (subscribe_hownow@16beavergroup.org).
Ok, looking forward to hearing back from everyone.
Ay + Rene
When 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: Gerrard on January 19, 2004 01:26 AMFor this program, it was a bit of overkill. It's a lot of overkill, actually. There's usually no need to store integers in the Heap, unless you're making a whole lot of them. But even in this simpler form, it gives us a little bit more flexibility than we had before, in that we can create and destroy variables as we need, without having to worry about the Stack. It also demonstrates a new variable type, the pointer, which you will use extensively throughout your programming. And it is a pattern that is ubiquitous in Cocoa, so it is a pattern you will need to understand, even though Cocoa makes it much more transparent than it is here.
Posted by: Mildred on January 19, 2004 01:27 AMOur 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: Adam on January 19, 2004 01:27 AMThis variable is then used in various lines of code, holding values given it by variable assignments along the way. In the course of its life, a variable can hold any number of variables and be used in any number of different ways. This flexibility is built on the precept we just learned: a variable is really just a block of bits, and those bits can hold whatever data the program needs to remember. They can hold enough data to remember an integer from as low as -2,147,483,647 up to 2,147,483,647 (one less than plus or minus 2^31). They can remember one character of writing. They can keep a decimal number with a huge amount of precision and a giant range. They can hold a time accurate to the second in a range of centuries. A few bits is not to be scoffed at.
Posted by: Guy on January 19, 2004 01:28 AM