http://www.unitedforpeace.org/nyc
646-473-8935
---------------------------------------------------
reminder>> CANDLELIGHT MARCH FOR PEACE
WHEN: Wed., March 5, gather at 5:30PM
WHERE: Assemble at Hillary Clinton's office, 780 Third Ave. (47th & 48th)
BRING: Candles, signs and drums
Leaflets & more info:
http://www.unitedforpeace.org/calendar.php?calid=2394
-----------------------------------------------------
In this update:
1) March 5 Student Walkouts, Candelight March, & More
2) NYC City Council Anti-War Resolution
3) March 8 Intl Women's Day Action in DC
4) March 9 Nonviolent Civil Disobedience in DC
5) March 15 Protest at the White House
6) March 22 NYC Anti-War March
7) What to do if war begins
8) How to get more involved with UFPJ NYC
9) If you had a bad police experience on Feb. 15
------------------------------------------------------
1) WED., MARCH 5 DAY OF ANTI-WAR ACTION **NYC Student Walkouts and Convergence of Student Strikers: http://www.unitedforpeace.org/calendar.php?calid=2453 **National Student Strike: http://www.unitedforpeace.org/students and http://www.nyspc.net **Candlelight March for Peace: http://www.unitedforpeace.org/calendar.php?calid=2394
2) NYC CITY COUNCIL ANTI-WAR RESOLUTION The NYC City Council has been waffling on passing an anti-war resolution -- while 124 other cities and counties have voiced opposition to Bush's war. A strong majority of New Yorkers oppose war on Iraq; our Councilmembers need to hear how we feel about their inaction! A vote is scheduled March 12 -- we need to raise the pressure. To get involved, send a blank email to nycantiwar-subscribe@yahoogroups.com or write to Tim Eubanks, tim@abffe.com
3) SAT., MARCH 8: WOMEN'S PEACE ACTION IN D.C. On International Women's Day, thousands of people will converge on Washington for a women-led action to encircle the White House. More info: http://www.unitedforpeace.org/article.php?list=sub&sub=16
4) SUN. MARCH 9: NONVIOLENT CIVIL DISOBEDIENCE IN D.C. Protests with nonviolent CD are being planned for the morning and afternoon on Sunday, March 9, in Washington DC by the Iraq Pledge of Resistance. Please see www.peacepledge.org/resist for more information, or contact Pledge Coordinator at pledgecoordinator@starpower.net.
5) SAT., MARCH 15: MARCH ON THE WHITE HOUSE Emergency national demonstration against the war in Washington, D.C. More info: http://www.unitedforpeace.org
6) SAT., MARCH 22: NYC MARCHES AGAINST THE WAR Gather on Fifth Avenue at 59th Street at noon for a major New York City anti-war march, to promote peace abroad and civil liberties at home. Leaflets and more info available soon at http://www.unitedforpeace.org/nyc
7) WHAT TO DO IF WAR BEGINS Converge on Times Square at 5pm on the day the bombing starts (the next day if bombing begins at night)
8) SOME WAYS TO PLUG IN TO UFPJ NYC * Organizing listserve (low-volume, announcements only): ufpjnyc-subscribe@yahoogroups.com * Volunteers listserve (average one email per day, containing specific requests for volunteer assistance) nycvolunteers-subscribe@yahoogroups.com * Outreach working group: ufpj-nyc-outreach-subscribe@yahoogroups.com * Arts & Culture working group: contact thomasg@speakeasy.net or greenelent@earthlink.net * Outreach and mobilizing meeting, next Tuesday, March 4, 6:30PM at the UFPJ office, 330 W. 42nd St, 8th floor; 646-473-8935
9) BAD POLICE EXPERIENCE ON FEB. 15? The New York Civil Liberties Union still wants to hear from anyone who had a bad experience with the police on February 15: nyclu215@aol.com
And UFPJ NYC still wants your February 15 stories -- we apologize to everyone who had their emails bounce back to them, in our post-protest fatigue we let a few details slip. You can re-send them to feb15@unitedforpeace.org
Posted by Brian Stefans at March 05, 2003 04:16 PMI WAS OUT WHEATPASTING ON THE 7TH WITH PEOPLE AFTER THE MEETING, AND IT WAS FUN!!!!
I'M NOT SURE IF I SIGNED VOLUNTEER SHEET, AND I'D LIKE TO DO IT AGAIN.
Ok
Posted by: Dave on November 29, 2003 07:35 AMBeing able to understand that basic idea opens up a vast amount of power that can be used and abused, and we're going to look at a few of the better ways to deal with it in this article.
Posted by: Noe on January 19, 2004 12:10 AMSince the Heap has no definite rules as to where it will create space for you, there must be some way of figuring out where your new space is. And the answer is, simply enough, addressing. When you create new space in the heap to hold your data, you get back an address that tells you where your new space is, so your bits can move in. This address is called a Pointer, and it's really just a hexadecimal number that points to a location in the heap. Since it's really just a number, it can be stored quite nicely into a variable.
Posted by: Guy on January 19, 2004 12:11 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: Morgan on January 19, 2004 12:12 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: Ciriacus on January 19, 2004 12:12 AMWhen 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: Cuthbert on January 19, 2004 12:12 AM