 |
|
|
Christopher Hitchens on the nature of generational identity -- which I myself always found rather silly, as if every poet born in 1926 had something to do with the others -- in his usual succinct terms. What does one do to become part of one's time, I guess is the question.
So let me ask you, how do you think you were affected by the sixties?
I have no choice but to put myself in a political generation. But I'm glad you say the sixties because I've always thought that of all the kinds of human solidarity, the generational is the lowest. (I wish I could find out the name of the person who said that.) Because what do you have to do except have an accident of birth? I mean, to be a sixties person, all you have to do is to be born in a certain year, like select wine, except not as good. To be a '68-er, however, a "soixante-huitard" -- we even have a French term for it now -- you have to have been someone who in some sense felt or saw the '68 crises coming, and was, in some sense, ready for it, or, if not that, was totally swept up in it, realized that here was a crux moment, a hinge year. I'm lucky in that I made my decision that I thought it was going to be key in '67, the year I went to Oxford actually, and joined a small Trotskyesque/Luxembourgist organization, which in the next year quadrupled ... no, much more than quadrupled its membership.
Conversation with Christopher Hitchens, p. 2 of 5
Posted by Brian Stefans at June 23, 2003 02:46 PM | TrackBackSeth Roby graduated in May of 2003 with a double major in English and Computer Science, the Macintosh part of a three-person Macintosh, Linux, and Windows graduating triumvirate.
Posted by: Blanche at January 18, 2004 09:25 PMEarlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.
Posted by: Marmaduke at January 18, 2004 09:25 PMLet's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.
Posted by: Garret at January 18, 2004 09:25 PMEarlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.
Posted by: Matthew at January 18, 2004 09:26 PMThe 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: Cuthbert at January 18, 2004 09:26 PM