The great Brazilian concrete poet Haroldo de Campos died last week.
I wish I could write an informative elegy about his life and career, but I admit to knowing very little about him except for the writings in the early concrete manifestos and the concrete poetry that appears in such books as the Mary Ellen Solt anthology of concrete poetry, all of which was really important to me at some point. You can now find all of this material on ubu.com, of course!
Marjorie Perloff wrote a somewhat disappointing essay about one his post-concrete works which can be found at her EPC homepage, "Concrete Prose": Haroldo de Campos's Galáxias and After" -- disappointing because, after a few rather abstract observations about his work that could have been applied to any number of other writers -- she doesn't read Portuguese, of course -- it just tails off into a discussion of Rosmarie Waldrop! At least that's my memory of it; I haven't reread it.
Other than that I've not seen a whole lot about him, though Northwestern (I believe) is putting out a collection of his writing in the near future -- that is very much something to look forward to, as he was one of the leading theorists (along with Pignitari, who I did meet and see read) of the bunch, and I think some of his ideas are more interesting than the work they produced (which nonetheless is still quite fascinating to me, even if I've leaned more on the Lettrists of late).
I have a few gorgeous, if gaudy, books by his younger brother Augusto de Campos, but like a dumbass, I lost his email address and haven't even been able to thank him for sending them to me!
But I did find one great essay in a Richard Kostelanetz anthology -- where else! -- that I wrote about in the long essays in Fashionable Noise about the computer poem, herewith called the "CP." The essay is composed entirely of paragraph long footnotes, which makes it a bit tough to read. Here's the entire one on the de Campos essay.
***
The CP, with its alien, fragmented but nonetheless consistent rhetorical strategies, requires new, somewhat clinical and analytical methods of reading, and probably the most important group of writers prior to the Language poets to systematically describe such methods from the viewpoint of artists were the Brazilian concrete poets, most importantly Haroldo de Campos. In “The Informational Temperature of the Text,” de Campos addresses the issue, raised by several critics of Concrete poetry, that the movement he help found was “impoverishing language”; his method for doing so is to take the term “impoverish” literally, and to determine where exactly the riches of a text might lie. His description of “informational temperature,” based on the writing of Max Bense, is as follows:
If we take 1 as the highest limit of a text’s informational temperature, that temperature, in a given text, will be higher the nearer it is to 1. In such cases, for Mandelbrot “the available words are ‘well employed,’ even rare words being utilized with appreciable frequencies. Low temperature, on the other hand, means that words are ‘badly employed,’ rare words being extremely rare.” Of the first case, Mandelbrot… gives James Joyce, whose vocabulary is “quite varied,” as the example; of the second, the language of children. (pp. 177-178)
That is why it rejects the airs and graces of crafsmanship – in spite of the seriousness with which it considers the artisan’s contribution to the stockpile of extant forms – from the art of verse to the elaborate diversificaiton of vocabulary in pose. It ahs recoure in its turn to factors of promximity and likeness on the grahpic-gestaltic plane, to elements of recurrence and reduncancy on the semantic and rhythmic plane, to a visual-ideogrammic syntax (when not merely “combinatory”) for controlling th flux of signs and rationalizing the sensible materials of a coposition. This is how it limits entropy (the tendency to dispersion, to disorder, to the –maximum informational potential of a system), fixing the informational temperature at the minimum necessary to obtain the aesthetic achievement of each poem undertaken. (179-180)
This 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: Ellen at January 18, 2004 10:29 PMSince 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: Daniel at January 18, 2004 10:30 PMThis 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: Salamon at January 18, 2004 10:30 PMThis is another function provided for dealing with the heap. After you've created some space in the Heap, it's yours until you let go of it. When your program is done using it, you have to explicitly tell the computer that you don't need it anymore or the computer will save it for your future use (or until your program quits, when it knows you won't be needing the memory anymore). The call to simply tells the computer that you had this space, but you're done and the memory can be freed for use by something else later on.
Posted by: Venetia at January 18, 2004 10:30 PMBeing 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: Zachary at January 18, 2004 10:31 PM