 |
|
|
[Tom Raworth sent this one in -- I'm posting it because I like the picture, and JK makes a good mate for Madame Sosostris.]
CNN.com - Kerouac bobblehead doll giveaway - Jul. 29, 2003
LOWELL, Massachusetts (AP) -- A homegrown literary icon will be remembered next month with an honor usually reserved for sports figures: a bobblehead doll.
The first 1,000 fans at the August 21 game between the Lowell Spinners and Williamsport Crosscutters of the Class A New York-Penn League will receive bobbing likenesses of Jack Kerouac.
The giveaway, in partnership with the English department at the University of Massachusetts at Lowell, is part of "Jack Kerouac Night" at LeLacheur Park.
The eight-inch doll features Kerouac holding a pen and notebook and standing on a copy of "On The Road," his best-known work.
"It's unusual, to say the least, to have a sports team get involved with a literary figure," said Hilary Holladay, director of the Kerouac Conference on Beat Literature.
Before he was a writer, Kerouac was a baseball fan and athlete. He excelled in football and track at Lowell High School, spent the winter of 1942 as a sportswriter for The Sun of Lowell, and played football at Columbia.
Posted by Brian Stefans at July 30, 2003 11:10 AM | TrackBackThe Stack is just what it sounds like: a tower of things that starts at the bottom and builds upward as it goes. In our case, the things in the stack are called "Stack Frames" or just "frames". We start with one stack frame at the very bottom, and we build up from there.
Posted by: Gentile at January 18, 2004 09:12 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: Lancelot at January 18, 2004 09:12 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: Jerome at January 18, 2004 09:12 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: Bridget at January 18, 2004 09:14 PMThat 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: Annabella at January 18, 2004 09:14 PM