AKMA's Random Thoughts

November 28, 2002

SBL Recap Part Two

For the afternoon, I dedicated some time to the book display and catching up on sleep. It had been a late night and an early morning (breakfast meetings need to start at 7 to allow enough time to eat, conduct business, and get to 9 AM sessions), and another late night lay ahead. Had dinner with my editor at Chalice Press, Jon Berquist, and his wife Sally (pastor of First Presbyterian Church, Flemington NJ). Dinner ran late, so we missed the Fortress Press reception, but nothing would keep us from the Brazos Press reception where we closed down the room along with several of our usual companions.

Sunday morning I had a meeting of the Editorial Board for Teaching Theology and Religion, then I presided at the first of a series of sessions on reading Scripture in the light of Derrida’s works. Daniel Boyarin, Regina Schwartz, Hugh Pyper, Tim Beal and Tod Linafelt, and David Jobling read papers; all were strong, and the impact of several observations stirred intense response (on which more later). Derrida himself could not make the session; he was sleeping off some jet lag, from having travelled over only the day before.

After lunch, I toured the book display again. This is not simple consumerism (I usually don’t buy much per hour at the display) but a social impulse, and an interest in keeping my blood flowing more steadily than results from sitting in sessions all day. I drifted up to our hotel room to check in with Margaret, who was working on the response she was going to read Monday morning to papers she hadn’t received until a week ago (and one of which she never received in advance).

Posted by AKMA at November 28, 2002 10:41 PM | TrackBack
Comments

Seth 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: Hercules at January 13, 2004 01:24 AM

The 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: Elizabeth at January 13, 2004 01:24 AM

When Batman went home at the end of a night spent fighting crime, he put on a suit and tie and became Bruce Wayne. When Clark Kent saw a news story getting too hot, a phone booth hid his change into Superman. When you're programming, all the variables you juggle around are doing similar tricks as they present one face to you and a totally different one to the machine.

Posted by: Blanche at January 13, 2004 01:24 AM

This 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: Adam at January 13, 2004 08:58 AM

When compared to the Stack, the Heap is a simple thing to understand. All the memory that's left over is "in the Heap" (excepting some special cases and some reserve). There is little structure, but in return for this freedom of movement you must create and destroy any boundaries you need. And it is always possible that the heap might simply not have enough space for you.

Posted by: Ebotte at January 13, 2004 08:59 AM

Note first that favoriteNumbers type changed. Instead of our familiar int, we're now using int*. The asterisk here is an operator, which is often called the "star operator". You will remember that we also use an asterisk as a sign for multiplication. The positioning of the asterisk changes its meaning. This operator effectively means "this is a pointer". Here it says that favoriteNumber will be not an int but a pointer to an int. And instead of simply going on to say what we're putting in that int, we have to take an extra step and create the space, which is what does. This function takes an argument that specifies how much space you need and then returns a pointer to that space. We've passed it the result of another function, , which we pass int, a type. In reality, is a macro, but for now we don't have to care: all we need to know is that it tells us the size of whatever we gave it, in this case an int. So when is done, it gives us an address in the heap where we can put an integer. It is important to remember that the data is stored in the heap, while the address of that data is stored in a pointer on the stack.

Posted by: Mildred at January 13, 2004 08:59 AM