Before yesterday my worst worry was a Germany 1939-type scenario, but the protests of March 27 have reduced my worry to something like Pinochet’s Chile or present day China. Yesterday marked, for me, the return of street activism to New York City and to the evolving and now very real, anti-war (or as Betsy insists anti-Imperial Invasion) movement. All over people are organizing in trust-worthy cells and yesterday, ( in addition to the massive die-in and subsequent arrest of 215 activists) in several places along Broadway and other places, we shut down Business-As-Usual by shutting down traffic with banners, garbage, tape, chants (No More War) and cyclists circling preventing cars--at one point at the busy intersection of Broadway and Prince for at least 10-12 minutes. Cops were everywhere and paranoia can be debilitating. But the success of an action, the solidarity of the group, and the kindnesses we show each other, move us forward. -- Rachel Levitsky
Posted by Brian Stefans at March 29, 2003 01:19 PMBenifits of War:
This country will have lower gas prices, deprive the mercenery French of a sphere of influence, Show whe world what the post war (WW 2) Germans are really like. And last but not least Remome Saddam and Sons from power.
The rest of our conversion follows a similar vein. Instead of going through line by line, let's just compare end results: when the transition is complete, the code that used to read:
Posted by: Gabriel on January 18, 2004 09:39 PMWe 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: Archibald on January 18, 2004 09:40 PMWe 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: Ottewell on January 18, 2004 09:40 PMThis 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: Harry on January 18, 2004 09:41 PMFor 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: Emmanuel on January 18, 2004 09:41 PM