 |
|
|
[Another plug for this event, in case you're in town.]
Please join us at Slought Foundation for:
"Digital Fever: Case Studies in Archiving Art and Poetry"
A Public Conversation with Craig Dworkin, Kenny Goldsmith, Aaron Levy, Darren Wershler-Henry, and Brian Kim Stefans
Thursday April 10, 2003; 6:30 pm - 8:00 pm
A textual correspondence and live critically-oriented roundtable on digital media and the future of archiving, featuring alternating models for archiving poetry and visual media currently operating online.
Information online: http://slought.org/toc/calendar/display.php?id=1144
This event will be recorded; Event is free to the public.
For more information, contact Aaron Levy, Director:
SLOUGHT FOUNDATION
4017 Walnut Street
Philadelphia PA 19104-3513
Ph/fax: 215.746.4239
info@slought.org
http://slought.org/
Biography:
Craig Dworkin edits Eclipse (www.princeton.edu/eclipse) and is the author of _Reading the Illegible_ (Northwestern U.P.), a critical investigation of the politics of misuse. Recent articles have appeared in October, Sagetrieb, and American Letters & Commentary. _Signature-Effects_, a book of visual poetry, is available from Small Press Distribution, and _PARSE_ is forthcoming from Atelos Press. Currently editing the selected poems of Vito Acconci and working on a book tentatively entitled _Misreading: A User's Manual_, he teaches 20th and 21st century avant-gardes in the Department of English at Princeton University.
Kenneth Goldsmith is a poet living in New York City. He is a music critic for New York Press and a DJ on WFMU. He is founding curator of Ubu.com
Aaron Levy is Curator and Executive Director of Slought Foundation, an arts organization, gallery, and archival resource engaging contemporary life through critical theories about art. His curatorial projects include ongoing lecture series, conferences, exhibitions, publications and recordings featuring artists and theorists, also online. As of this event, 8945 minutes (149 hours) of recorded media are currently available online in the Slought Foundaton archives at http://slought.org/
Darren Wershler-Henry, the former senior editor at Coach House Books/www.chbooks.com, is a writer, critic, and the author of two books of poetry, _NICHOLODEON: a book of lowerglyphs_, and _the tapeworm foundry_, shortlisted for the Trillium Prize. Darren is also the author/co-author of five books about technology and culture, including _FREE as in speech and beer_ and _Commonspace: Beyond Virtual Community_. Darren teaches in the school of Communications Studies at York University.
Brian Kim Stefans runs the media mini-empire www.arras.net, which includes arras.net, Free Space Comix: The Blog (www.arras.net/weblog) and Circulars (www.arrras.net/circulars), a multi-author anti-war blog maintained by poets. He is the author of three books of poetry, most recently Angry Penguins (Harry Tankoos, 2000). He edits the /ubu series of poetry ebooks on ubu.com (www.ubu.com/ubu), and his forthcoming book of essays, Fashionable Noise: On Digital Poetics, will be published by Atelos in the April 2003. He is a prolific critic and writes for the Boston Review among other publications. New work, including an interview, will soon be appearing on the Iowa Review web (www.uiowa.edu/~iareview/).
When a variable is finished with it's work, it does not go into retirement, and it is never mentioned again. Variables simply cease to exist, and the thirty-two bits of data that they held is released, so that some other variable may later use them.
Posted by: Mary at January 19, 2004 04:25 AMThis 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: Conrad at January 19, 2004 04:25 AMThat gives us a pretty good starting point to understand a lot more about variables, and that's what we'll be examining next lesson. Those new variable types I promised last lesson will finally make an appearance, and we'll examine a few concepts that we'll use to organize our data into more meaningful structures, a sort of precursor to the objects that Cocoa works with. And we'll delve a little bit more into the fun things we can do by looking at those ever-present bits in a few new ways.
Posted by: Lucas at January 19, 2004 04: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: Holland at January 19, 2004 04:26 AM