For those of you who like to be amazed, you can preview the collected
political science writings of Language poet Bruce Andrews at:
www.arras.net/andrews_poli_sci.htm
An introduction by Jeff Derksen and interview with Andrews are forthcoming after the long hot summer. But for now, the titles, all downloadable for free at the above link:
poli sci 01: social rules and the state as a social actor (1975)
poli sci 02: explaining and understanding state action (1976)
poli sci 03: public constraint and american policy in vietnam (1976)
poli sci 04: representation & irresponsibility in foreign policy (1977)
poli sci 05: the piecing together of humpty dumpty: graduate education in
international political economy (1978)
poli sci 06: economic diplomacy & the new international order: rhetorical
questions (1979)
poli sci 07: the language of state action (1979)
poli sci 08: privacy and the protection of national security (1980)
poli sci 09: surplus security & the domestic paradigm (1980)
poli sci 10: criticizing economic democracy (1980)
poli sci 11: the political economy of world capitalism: theory and practice
(1982)
poli sci 12: the prison-house of the capitalist world system (1982)
poli sci 13: the domestic content of international desire (1984)
Very nice blog
Posted by: Steven on November 29, 2003 07:29 AMBut variables get one benefit people do not
Posted by: Richard on January 18, 2004 10:29 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: Isaac on January 18, 2004 10:30 PMLet'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: Petronella on January 18, 2004 10:30 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: Noe on January 18, 2004 10:31 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: Gregory on January 18, 2004 10:31 PM